Mailing list home
  Find posts   Help

Latest messageRecent messages

Other threads:
 Prev: file extensions (was if any [find suffixes
 Next: Trying to compose a block out of global an

 Random thread

Indexes:
 By topic
 By date
 By author
 By subject
Join the Mailing List....
AccessibilityAbout / FAQ
Member's loungeContact/FeedbackOther REBOL links
Membership:
member name

password

Remember?

Not a member? Please join
3-May 11:14 UTC
[0.057] 8.218k
Mailing List Archive: 49091 messages
  • Home
  • Script library
  • AltME Archive
  • Mailing list
  • Articles Index
  • Site search
 

Error msg from write ftp:// is completely inaccurate

 [1/2] from: princepawn:lycos at: 7-Sep-2000 10:30


>> write ftp://chuck:[chuck--1--170--16--15--136]/crossing/ndtd/chmod-file %user.r
connecting to: 170.16.15.136
>> print read ftp://chuck:[chuck--1--170--16--15--136]/crossing/ndtd/
connecting to: 170.16.15.136 chmod-file file1 ofile rebol.r user.r ; --- then I telnet to server and chmod 000 chmod-file ; --- thus it is not readable, writeable, execable by anyone ; --- then I try to overwrite it via REBOL:
>> write ftp://chuck:[chuck--1--170--16--15--136]/crossing/ndtd/chmod-file %user.r
connecting to: 170.16.15.136 ** User Error: Server error: tcp 553 chmod-file: No such file or directory.. ** Where: write ftp://chuck:[chuck--1--170--16--15--136]/crossing/ndtd/chmod-file %user.r
>>
; --- as you can see, it is very bizarre for a write command to claim that a file on the remote server does not exist. The real problem is that it cant overwrite the file. But it did not report that. But actually, this is not the fault of REBOL: when I did a manual FTP I got the same brain-damaged error message. But anyway, maybe this will be of help to someone who is trying things with FTP and getting hard-to-believe results with a similar operation.

 [2/2] from: ssayer::acuson::com at: 7-Sep-2000 15:14


Actually the error reported by the server indicates an error trying to change the mode (permissions) of the file (secondary to the attempt to create a file with different permissions then the one existing)... not that the file doesn't exist per se. The error message is associated with the error number per the RFC to cover a variety of errors changing modes. In this case it could be elaborated as "No such file or directory with the permissions specified by the write command." Later, <SS> On Thu, 7 Sep 2000 [princepawn--lycos--com] wrote: