Dan Jacobson <[EMAIL PROTECTED]> writes: > Man says: > -T seconds ... The default timeout is 900 seconds > > Ok, then why does this take only 3 minutes to give up?: [...]
Several reasons. * The default timeout is 900 seconds only for read timeouts. There is no default timeout for connect and for DNS lookups. This means that, as far as Wget is concerned, the call to connect can take forver. * The system may choose to terminate connect after a time period. While an application can shorten the connect time, there is normally no way to lengthen it. See Stevens's answer to a question in the Socket FAQ: <http://www.ibrado.com/sock-faq/#faq36>. NB, Wget uses a modified version of the alarm-based approach to implement connect timeouts. In other words, if your system's TCP implementation decides to give up the connect after three minutes, there's nothing Wget can do about it -- except try again, which seems to be what Wget does, based on the output you provided. * None of this applies to Wget 1.8.2 which doesn't even implement connect timeouts! (I noticed that you're using 1.8.2 only after writing the above explanations.) Please try it with 1.9. > I want to limit that 3 minute above timeout to only 30 seconds `-T 30' should work in 1.9. Just try it. However... > but it appears -T is not the one affecting this case, or else it > should have waited 15 minutes as documented. ...the timeout still cannot be lengthened to 15 minutes, as explained above. > $ wget --version > GNU Wget 1.8.2 ... > Originally written by Hrvoje Niksic <[EMAIL PROTECTED]>. > > I'd put the bug address there too or instead. `wget --help' gives one, but good point.
