Lee Haywood <[email protected]> writes: > I've always had this problem, where the web server is busy and does > not accept() the incoming connection from wget. In this case using > the -T switch to set all the timeouts makes no difference, since wget > simply hangs and doesn't timeout as you'd expect it to. Presumably > this is because the DNS is okay and the read() never starts, but the > connect timeout relies on a library which doesn't implement the > timeout?
Actually, Wget tries hard to implement the timeout in all of DNS, connect(), and read(). If that doesn't work, it's a bug. > Obviously this is an issue with scripts that want to avoid taking > forever and give wget explicit timeouts, but lock-up regardless. > Tested on version 1.12 on Xubuntu. Can you specify how you test this, exactly? An strace dump of the running Wget process might also help in debugging the problem.
