I don't think the FAQ covers this and I can't see anything in the archives on it under two years old. Mind you, that may just mean it was fixed in 3.2beta two years ago 8-)
This is 3.1.5 (yes, I know the security concerns and have checked the exploits don't get through our perl wrapper) on Intel Linux (Debian). <timeout> is defaulted (30 seconds) but I note that it refers to a timeout on a TCP/IP read. I'm finding that the timeout on a failure to set up a TCP/IP connection is about 10 or 12 minutes - it doesn't take many unresponsive servers (among the 600 I'm indexing) to add an hour or two to the htdig run! Is there a known solution to this? Maybe it's a system timeout setting that I need to get changed? regards, Malcolm. Malcolm Austen, Tel: +44(0) 1865 273216 Oxford University Computing Services, Fax: +44(0) 1865 273275 13 Banbury Road, Email - [EMAIL PROTECTED] Oxford, OX2 6NN, England WWW - http://users.ox.ac.uk/~malcolm/ ------------------------------------------------------- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 _______________________________________________ htdig-general mailing list <[EMAIL PROTECTED]> To unsubscribe, send a message to <[EMAIL PROTECTED]> with a subject of unsubscribe FAQ: http://htdig.sourceforge.net/FAQ.html
