Herold Heiko <[EMAIL PROTECTED]> writes:
> Just wondering, and my knowledge of this stuff is too shallow... anobody
> would care to explain me
>
>
> --10:11:46-- http://1.2.3.4/some.file
> => `1.2.3.4/some.file'
> Connecting to 1.2.3.4...
> connect: No such file or directory
> Retrying.
>
> Sorry for changed IP ecc, I've only a mail of this happening when
> people tried to suck stuff from a (you guessed it) a porn site,
> probably not any more existant.
Heh, feel free to forward the real address so we can "test" the
problem. :-) (Sorry, couldn't resist.)
Grepping Wget sources for "No such file or directory" is a mistake
because Wget always lets the system routines print out the correct
error message according to the errno status after a function has
failed.
Thus "No such file or directory" after connect() simply means that
the connect() call returned -1 and errno ended up being set to ENOENT.
This is either an OS bug (if a function returns -1, it *must* also set
errno), or a Wget bug where the state of errno changed between the
call to connect() and the code which prints the error message.
> second thing, if really there was a connection, a message "no such file"
> , wget shouldn't retry I suppose.
Wget retried because it was confused by the unknown error and assumed
it was transient.
What OS are you using?
What version of Wget are you using?
> Update: I convinced the guy to give me the url, even stranger: while
> he tried to get http://209.237.156.182:8080/000707.mpg it seems you
> can specifiy any file on that ip:port to get the same result. Note:
> currently I can't ping that host, traceroute does timeout ecc.
I get this:
{florida}[~/work/try/wget-hack/build/src]$ ./wget
http://209.237.156.182:8080/000707.mpg
--13:00:44-- http://209.237.156.182:8080/000707.mpg
=> `000707.mpg'
Connecting to 209.237.156.182:8080...
connect: No route to host
Retrying.
Looks correct to me.
