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://<user>:<pass>@<ip>:11111/<dir>/
(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://<user>:<pass>@<ip>:11111/<dir>/") -> host
newpath: /<dir>/
�.listing� als tempor�re Auflistungsdatei benutzen.
--05:20:41-- ftp://<user>:<pass>@<ip>:11111/<dir>/
=> `.listing'
Verbindungsaufbau zu <ip>:11111... Created fd 4.
verbunden!
Anmelden als <user> ... 220 BulletProof FTP Server ready ...
--> USER <user>
331 Password required for <user>.
--> PASS <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
