He promised to send a netstat report when he does his next dig. Open
connections aren't a great thing, especially since it's slowing down
the servers it's indexing.
-Geoff
>From: Steven Karel <[EMAIL PROTECTED]>
>X-Sender: [EMAIL PROTECTED]
>To: Geoff Hutchison <[EMAIL PROTECTED]>
>Subject: Re: [htdig] htdig pausing with each new server
>
>On Tue, 5 Oct 1999, Geoff Hutchison wrote:
>
> > At 10:00 AM -0400 10/5/99, Steven Karel wrote:
> > >If htdig isn't multithreaded, that's a problem -- I wish I had the time
> > >and expertise to help. But I'm still curious -- if it isn't multithreaded,
> > >how does it open dozens of simultaneous connections when it's in the
> > >retrieval part of the dig (as opposed to the server identification part)?
> >
> > It doesn't open dozens of simultaneous connections! It only opens a
> > connection for each file. Granted it generally flies through indexing
> > each file, but there shouldn't be dozens of simultaneous connections.
>
>It does create dozens of simultaneous connections (one for each file,
>but many connections to each server) -- possibly through the
>failure to close the connections it opens? At one point I got yelled at by
>one of the other sysadmins for a denial-of-service attack on his webserver
>-- it had hundreds of open connections. Increasing server-wait-time helped
>with that, but I still find that if I look with netstat while htdig is
>running that there are a large number (dozens) of connections attributable
>to htdig.
------------------------------------
To unsubscribe from the htdig3-dev mailing list, send a message to
[EMAIL PROTECTED] containing the single word "unsubscribe" in
the SUBJECT of the message.
