On Tue, 13 Apr 2004, Josh Santangelo wrote: > build connection with principa.net:80 > no server running > 467:467:5:http://principa.net/tours/d4/d4qt_page2.php: no server running > 468:468:5:http://principa.net/tours/d4/d4qt_page6.php: no server running > 469:469:5:http://principa.net/tours/d4/d4qt_page8.php: no server running > > I've set it up to make only one request every two seconds, on the > suspicion that it was just hitting the site too fast, but that didn't > seem to help. When rundig isn't able to connect, I'm able to get to the > site from a browser just fine. Has this sort of problem been seen > before? Is there an easy fix?
What version of ht://Dig are you using? If it is one of the 3.2 betas, you might want to take a look at the max_retries attribute. http://www.htdig.org/dev/htdig-3.2/attrs.html#max_retries Otherwise I don't know of an easy fix on the ht://Dig side. The output implies that for some reason the server was not able to provide a valid connection for an htdig request. The htdig response to this situation, prior to 3.2, is to treat all future requests associated with that server as if the server is no longer running. Jim ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ ht://Dig general mailing list: <[EMAIL PROTECTED]> ht://Dig FAQ: http://htdig.sourceforge.net/FAQ.html List information (subscribe/unsubscribe, etc.) https://lists.sourceforge.net/lists/listinfo/htdig-general
