On Thu, 15 Aug 2002, Geoff Hutchison wrote: + That's not the only reason to upgrade to 3.1.6...
Sure, but it was the single most powerful point ... + > Is there a known solution to this? Maybe it's a system timeout setting + > that I need to get changed? + + Nope. The connection code was changed in 3.1.6 and should handle + timeouts and unresponsive servers better. See the release notes for a + whole pile of more fixes. <http://www.htdig.org/RELEASE.html> ... Now I've quantified the time lost waiting on unresponsive servers and concluded the upgrade may cut 5 or 6 hours off my elapsed dig time if it saves 9 or 10 minutes on every unresponsive server. Trouble is that I'm not sysadmin, I look after htdig as an application. 3.1.6 was being held off to await a change of hardware but this may be the lever I need to get 3.1.6 without waiting for the (delayed) hardware change 8-) Ta. regards, Malcolm. [EMAIL PROTECTED] 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
