Very Computer

Hi,

My problem only exist under File Commander version 1.40 and beyond.
Specifically, my problem is with copying a file from my local drive to
my network drive running Linux Slackware (2.0.0) NFS server. The file
gets copied but it has zero bytes. The NFS Control Program window
displays this message:

"Open (filename) : Failed to create file."

The File Commander displays "Access denied". I click OK and the file got
copied but the length is zero.

I go over to my Linux server and the file is there with zero length and
the permission bits are all zeros.

I seem to have isolated the problem to File Commander since I don't get
this problem when I do the "copy" from the command line. The file gets
copied to my network drive with the correct permission bits.

(BTW, I don't have this problem when I copy from my network drive to my
local drive. It's only when I copy FROM my local drive TO my network
drive).

I appreciate your help.

Thanks.

Hi,

My problem only exist under File Commander version 1.40 and beyond.
Specifically, my problem is with copying a file from my local drive to
my network drive running Linux Slackware (2.0.0) NFS server. The file
gets copied but it has zero bytes. The NFS Control Program window
displays this message:

"Open (filename) : Failed to create file."

The File Commander displays "Access denied". I click OK and the file got
copied but the length is zero.

I go over to my Linux server and the file is there with zero length and
the permission bits are all zeros.

I seem to have isolated the problem to File Commander since I don't get
this problem when I do the "copy" from the command line. The file gets
copied to my network drive with the correct permission bits.

(BTW, I don't have this problem when I copy from my network drive to my
local drive. It's only when I copy FROM my local drive TO my network
drive).

I appreciate your help.

Thanks.

: displays this message:

: "Open (filename) : Failed to create file."

: I go over to my Linux server and the file is there with zero length and
: the permission bits are all zeros.

: I seem to have isolated the problem to File Commander since I don't get
: this problem when I do the "copy" from the command line. The file gets
: copied to my network drive with the correct permission bits.

: (BTW, I don't have this problem when I copy from my network drive to my
: local drive. It's only when I copy FROM my local drive TO my network
: drive).

i have a similar problem spooling files from pc's using hclnfsd.  the pc
client requests a spool file, the file is created with zero length and
all permission bits set to zero.  the hclnfsd log file shows that the spool
file creation was successful and that the file was successfully spooled.
the pc client is unable to write to the file and returns either a "disk full"
message (win 3.1 clients) or "insufficient permissions/authorization failure"
on win nt clients.  oh, yes, the files are created as user "nobody."

could there be a commonality between these two problems?

carl

carl g. riches
university of washington

box 352181                      voice:    206-543-0562
seattle, wa 98195-2181          fax:      206-685-0666