> > The important thing is not whether that fails. I'm fine with it > failing, as long as it 1) returns an error code and 2) doesn't change > the current directory. > > An ftpd that 1) returned success or 2) changed to some random directory > while returning an error must be buggy. Could you check your server? > It should return some error code and PWD should not change. > > -- > Nate > Hi Nate, Here's what it did: Connected to zos.dignus.com. 220-FTPD1 IBM FTP CS V1R5 at P390.dignus.com, 18:17:50 on 2007-03-29. 220 Connection will close if idle for more than 5 minutes. Name (flexes:rivers): rivers 331 Send password please. Password: 230 RIVERS is logged on. Working directory is "RIVERS.". Remote system type is MVS. ftp> pwd Remote directory: 'RIVERS.' ftp> cd test/obj 501 A qualifier in "test/obj" contains an invalid character ftp> pwd Remote directory: 'RIVERS.' ftp> quit - Dave Rivers - -- rivers@dignus.com Work: (919) 676-0847 Get your mainframe programming tools at http://www.dignus.com _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"

The mainframe (z/OS) FTP server does not allow multiple "directories" in CWD command. This is due to the mapping of "directories" to flat file names in the z/OS dataset-name convention. So - while I can say: ftp> cd RIVERS ftp> cd TEST ftp> cd OBJ which results in the current working "directory" being RIVERS.TEST.OBJ. I cannot say ftp> cd RIVERS/TEST/OBJ But, I _could_ say: ftp> cd RIVERS.TEST.OBJ So - on "different" systems where the idea of "directory" has to be mapped onto a foreign filesystem, you can get interesting results. This may or may-not matter... I was just citing an example. - Dave Rivers - -- rivers@dignus.com Work: (919) 676-0847 Get your mainframe programming tools at http://www.dignus.com _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"