On Tue, Dec 11, 2001 at 07:34:54PM +0300, Alexander V. Lukyanov wrote:
> > That didn't fix it, though. Both cases still stall for a second for me.
>
> I have added Fg/Bg, but forgot to set priority on newly created session.
It still didn't work.
01:51pm [EMAIL PROTECTED]/2 [~/lftp/src] ./lftp 0
lftp 0:~> de 5
lftp 0:~> set net:connection-limit 1
lftp 0:~> mkdir a b &
[0] mkdir a b &
`a' [Not connected]
---- Connecting to 0 (0.0.0.0) port 21
<--- 220-
<--- 220 Server ready.
---> USER anonymous
<--- 331 Anonymous login ok, send your complete email address as your password.
---> PASS lftp@
<--- 230 Anonymous access granted, restrictions apply.
---> PWD
<--- 257 "/" is current directory.
---> MKD a
<--- 550 a: Permission denied
mkdir: Access failed: 550 a: Permission denied
---> MKD b
<--- 550 b: Permission denied
mkdir: Access failed: 550 b: Permission denied
lftp 0:~>
[0] Done (mkdir a b)
lftp 0:/> mkdir a b &
[0] mkdir a b &
`a' [Connections limit reached]
(~1 second delay)
---> MKD a
<--- 550 a: Permission denied
mkdir: Access failed: 550 a: Permission denied
---> MKD b
<--- 550 b: Permission denied
mkdir: Access failed: 550 b: Permission denied
> I have applied the patch (without some changes). Then I fixed dirname_alloc;
depth_first: I changed this because it's confusing; it seems that if
this is false, it'll be a breadth-first traversal (which it's not, of
course.)
GetFileInfo should probably fail here:
lftp :~> cls -ld ~
~/
lftp :~> cls -ld /
//
(we're not actually connected)
Another symptom:
lftp :~> find
./
find: Not connected
Probably related:
01:59pm [EMAIL PROTECTED]/2 [~/lftp/src] ./lftp foo@0
Password:
lftp foo@0:~> de 5
lftp foo@0:~> find
./
---- Connecting to 0 (0.0.0.0) port 21
<--- 220-
<--- 220 Server ready.
---> AUTH TLS
<--- 234 AUTH TLS successful
---> PBSZ 0
<--- 200 PBSZ 0 successful
---> USER foo
<--- 331 Password required for foo.
---> PASS XXXX
<--- 530 Login incorrect.
(^Z)
[0] find &
.: Delaying before reconnect: 55 [Delaying before reconnect: 55]
Persist is off, of course.
(Oops, also getting a dupe status somewhere. Less important, though.)
Last: Spurious "%2F/":
01:24pm [EMAIL PROTECTED]/2 [~/lftp/src] ./lftp
lftp :~> find ftp://localhost
ftp://localhost/%2F/
---- Connecting to localhost (127.0.0.1) port 21
ftp://localhost/3x3.avi
Second time (same session), spurious slash is still there but %2F is
gone:
lftp :~> find ftp://localhost
ftp://localhost//
ftp://localhost/3x3.avi
We probably shouldn't have an extra slash or %2F in either of these
cases, since it wasn't there in the argument. (Just one slash, because
it's a directory.)
--
Glenn Maynard
