> I tried adding "timeout: 10" in the config but it > doesnt seem to help.
You haven't mentioned what version of htdig you're using. In particular, the TCP code was improved in the 3.1.6 production release (relative to other 3.1.x releases) and should also be more reliable in the 3.2 betas. In particular, it seems that the older method of setting TCP timeouts used prior to 3.1.6 and (IIRC) 3.2.0b3 doesn't work on many OSes. So the newer code sets an alarm(), which seems more reliable. If you're using 3.1.6, please let us know, as well as more information about your setup (OS version, installed by binary or source...). -- -Geoff Hutchison Williams Students Online http://wso.williams.edu/ ------------------------------------------------------- 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
