R
rcurzon
Guest
I try to use NCFTP client (windows) to upload to a unix system. I am
trying the "-X" options to rename a file after upload via RNFR/RNTO.
In effect, I move it from a subdirectory into the parent directory.
This ony appears to work if the sub and parent have 777 permissions,
when I reduce to 755 it fails.
The error is superficially unrelated, it appears to upload the file
and then fail to confirm success.
2007-11-18 20:32:48 Eastern Standard Time [$00000bbc] | 150: Opening
BINARY mode data connection for myfile.bin
2007-11-18 20:55:05 Eastern Standard Time [$00000bbc] | Could not
read reply from control connection -- timed out.
2007-11-18 20:55:05 Eastern Standard Time [$00000bbc] | Error (-132)
occurred on myfile.bin: could not send file to remote host
2007-11-18 20:55:05 Eastern Standard Time [$00000bbc] | Rescheduled
myfile.bin
Then it retries, finds the file is already uploaded, and quits without
ever executing the RNFR/RNTO.
If I change the sub and parent to 777, everything executes without a
hitch.
That sounds wrong to me, is it an NCFTP bug?
tks
Richard
trying the "-X" options to rename a file after upload via RNFR/RNTO.
In effect, I move it from a subdirectory into the parent directory.
This ony appears to work if the sub and parent have 777 permissions,
when I reduce to 755 it fails.
The error is superficially unrelated, it appears to upload the file
and then fail to confirm success.
2007-11-18 20:32:48 Eastern Standard Time [$00000bbc] | 150: Opening
BINARY mode data connection for myfile.bin
2007-11-18 20:55:05 Eastern Standard Time [$00000bbc] | Could not
read reply from control connection -- timed out.
2007-11-18 20:55:05 Eastern Standard Time [$00000bbc] | Error (-132)
occurred on myfile.bin: could not send file to remote host
2007-11-18 20:55:05 Eastern Standard Time [$00000bbc] | Rescheduled
myfile.bin
Then it retries, finds the file is already uploaded, and quits without
ever executing the RNFR/RNTO.
If I change the sub and parent to 777, everything executes without a
hitch.
That sounds wrong to me, is it an NCFTP bug?
tks
Richard