On Sat, Dec 22, 2001 at 08:53:08PM +0100, Piotr Krukowiecki wrote:
> New info, just noticed: lftp is cd'ing to non existing directory
>
> lftp [EMAIL PROTECTED]:/> ls
> ---> PASV
> <--- 227 Entering Passive Mode (127,0,0,1,7,146).
> ---- Connecting data socket to (127.0.0.1) port 1938
> ---> LIST
> <--- 150 Opening ASCII mode data connection for /bin/ls.
> ---- Closing data socket
> total 16
> drwxr-xr-x 1 root root 4096 Dec 22 17:46 in_progress
> drwxr-xr-x 0 root root 4096 Dec 22 19:13 pub
> drwxr-xr-x 0 root root 4096 Dec 22 20:43 test
> drwxr-xr-x 0 root root 4096 Dec 21 21:54 users
> [here and everywhere below cutted 226 stuff]
> lftp [EMAIL PROTECTED]:/> cd test
> ---> CWD /test
> <--- 250 Changed directory successfully to '/test'.
> cd ok, cwd=/test
> lftp [EMAIL PROTECTED]:/test> ls
> ---> PASV
> <--- 227 Entering Passive Mode (127,0,0,1,7,150).
> ---- Connecting data socket to (127.0.0.1) port 1942
> ---> LIST
> <--- 150 Opening ASCII mode data connection for /bin/ls.
> ---- Closing data socket
> total 0
> lftp [EMAIL PROTECTED]:/test> cd x
> ---> CWD /test/x
> <--- 250 Changed directory successfully to '/test'.
> cd ok, cwd=/test/x
> lftp [EMAIL PROTECTED]:/test/x> pwd
> ftp://piotr:[EMAIL PROTECTED]:4760/%2Ftest/x
> lftp [EMAIL PROTECTED]:/test/x> ls
> ---> PASV
> <--- 227 Entering Passive Mode (127,0,0,1,7,154).
> ---- Connecting data socket to (127.0.0.1) port 1946
> ---> LIST
> <--- 150 Opening ASCII mode data connection for /bin/ls.
> ---- Closing data socket
> total 0
> lftp [EMAIL PROTECTED]:/test/x>
There's absolutely nothing wrong with lftp's behavior here. "250" means
the CWD command was successful: the directory specified (/test, /test/x)
exists and was CD's into.
If this server is returning 250 when it doesn't exist, expecting the
client to see the changed directory in the message, it's an incredibly
broken server, and I don't think we should even attempt to work around
this.
> > Er, it shouldn't be sending ~ in CWDs. This from CVS?
>
> irrc yes, but 2.4.8 does this too.
>
>
> Hmm cvs version (statically compilled) dumps core when connecting to ftp
> server:
>
> ---- Connecting to 127.0.0.1 (127.0.0.1) port 4760
> <--- 220 Local time is Sat Dec 22, 2001 20:48.
> ---> USER piotr
> <--- 331 Password required for piotr.
> ---> PASS XXXX
> <--- 230
> ---> PWD
> <--- 257 "/users/piotr" is current directory.
> Segmentation fault (core dumped)
>
> The '"/users/piotr"' is white (ie this ftp uses colors)
> When i disable using colors, it's not segfaulting
> 2.4.8 doesn't segfaults at all.
Hmm. It's probably failing to parse the directory response, and this is
probably why it's sending ~'s. This might be tricky to work around;
filenames can have real ANSI in them.
> queue get sth1
> queue get sth2
> won't notify you when sth1 is downloaded.
Well, maybe we should have a report-transfer-completion {yes,no,fg},
the latter being the current behavior (which I would prefer to be the
default.)
--
Glenn Maynard
