Re: Problems with wget <-> Bulletproof ftpd (Win32)
At 09:55 13.06.01 +0200, you wrote: > > 421 Too many users logged for this account. Try again later. >That's it. You are logged in more times than that you are allowed to. >Seems clear to me. No, my point was that wget should retry here at this point. > > Is this a known issue? Perhaps it's more a wrong behaviour of Bulletproof > > instead of wget, but since i'm not sure about that, i decided to post it > > here :) > >We can easily verify that: In the moment when your wget session fails, >just try a normal FTP session (possibly without any proxies inbetween as >this may cause additional problems). If, after your login, the FTP >session fails as well, it's the Bulletproof FTPd. Otherwise it may be >some problem in wget (although I personally doubt it). In such a case >please send us a complete log of that "normal" FTP session with "set >debug on" so that we can compare what is going wrong. What i meant was, that Bulletproof ftpd perhaps sends its commands in a non-conformal way, and thus wget is "confused". Don't ask me about the official rules of ftp-commands when setting up a connection, but perhaps it's wrong to ask wget about the password, instead of saying "too many users" just after the username has been posted. If so, perhaps wget could be rewritten in that way, that it retries also when retrieving this commands of bulletftpd? bye Stefan
Re: Problems with wget <-> Bulletproof ftpd (Win32)
At 22:34 14.06.01 +0200, you wrote: >Jan Prikryl <[EMAIL PROTECTED]> writes: > > >> 421 Too many users logged for this account. Try again later. > > > > That's it. You are logged in more times than that you are allowed to. > > Seems clear to me. > >I think his point is that Wget should retry. And there he is right -- >Wget's FTP code was meant to retry in such cases, but it doesn't >always work. That was exactly was i meant, sorry if my first post was misleading. In my opinion it should retry, and it usually does with other ftpds (e.g. Serv-U Win32, just to name one). The main difference in the sent ftp commands with bulletproof ftpd is that wget has to send user AND pass, whereas with other ftpds, where wget behaves correclty, only the username is sent, and immediately the response "too many users" is received. bye Stefan Gärtner
Re: Problems with wget <-> Bulletproof ftpd (Win32)
Jan Prikryl <[EMAIL PROTECTED]> writes: >> 421 Too many users logged for this account. Try again later. > > That's it. You are logged in more times than that you are allowed to. > Seems clear to me. I think his point is that Wget should retry. And there he is right -- Wget's FTP code was meant to retry in such cases, but it doesn't always work.
Re: Problems with wget <-> Bulletproof ftpd (Win32)
Dings-Da wrote: > I got a question on Wget's behaviour with Windows-based Bulletproof FTPd. > Though i am aware that wget had some problems with Windows-based ftp > servers, which were quite often discussed here in the mailing list, i tried > out the latest wget-version v1.7 (not dev!) and encountered the following: > > [...] > > 421 Too many users logged for this account. Try again later. That's it. You are logged in more times than that you are allowed to. Seems clear to me. > Is this a known issue? Perhaps it's more a wrong behaviour of Bulletproof > instead of wget, but since i'm not sure about that, i decided to post it > here :) We can easily verify that: In the moment when your wget session fails, just try a normal FTP session (possibly without any proxies inbetween as this may cause additional problems). If, after your login, the FTP session fails as well, it's the Bulletproof FTPd. Otherwise it may be some problem in wget (although I personally doubt it). In such a case please send us a complete log of that "normal" FTP session with "set debug on" so that we can compare what is going wrong. -- jan
Problems with wget <-> Bulletproof ftpd (Win32)
Hey,
I got a question on Wget's behaviour with Windows-based Bulletproof FTPd.
Though i am aware that wget had some problems with Windows-based ftp
servers, which were quite often discussed here in the mailing list, i tried
out the latest wget-version v1.7 (not dev!) and encountered the following:
When starting the command (both on linux and solaris8-systems - with and
without firewalls):
wget --passive-ftp --wait=70 --waitretry=61 -t0 -c -r -np -nd -N -d
ftp://:@:1//
(also happens when leaving out --passive-ftp/-c/-r/-N/-np/-nd)
--Output start-
DEBUG output created by Wget 1.7 on linux-gnu.
parseurl ("ftp://:@:1//") -> host
newpath: //
».listing« als temporäre Auflistungsdatei benutzen.
--05:20:41-- ftp://:@:1//
=> `.listing'
Verbindungsaufbau zu :1... Created fd 4.
verbunden!
Anmelden als ... 220 BulletProof FTP Server ready ...
--> USER
331 Password required for .
--> PASS
421 Too many users logged for this account. Try again later.
Fehler bei der Anmeldung.
Closing fd 4
unlink: Datei oder Verzeichnis nicht gefunden
BEENDET --05:20:42--
Geholt: 0 Bytes in 0 Dateien
--Output end-
Is this a known issue? Perhaps it's more a wrong behaviour of Bulletproof
instead of wget, but since i'm not sure about that, i decided to post it
here :)
Sorry about the german debug-text, but most of it should be self-explantory :)
BTW, sometimes the debug list "fd3" instead of "fd4"
bye
Stefan Gärtner
Germany
