Re: Squid connection retry problem -- fd leak?

On Mon, 15 Sep 1997, WWW server manager wrote:
> After my earlier messages, I tried 1.NOVM.16 + retry patch (Oskar Pearson's
> version) for a few hours, but backed off to 1.NOVM.16 without the patch as it
> rapidly became clear the problem was still there. cache.log does not show *any*
> retries during the time I was running with the retry patch, but the problem
> still happened...

The possibility of a dup() bug in Solaris is intriguing, but dup2() is
never called unless there's a connection retry, reflected in the cache.log
file by:

97/09/15 08:18:50| commConnectHandle: FD 22 206.64.127.33 conn fail, retrying

Right after this message appears, the FD-22 is dup2()'d and reset for
another connection attempt. If there's "grep retry cache.log" doesn't
turn up anything, then for the most part the behaviour of Squid is the
same as before the patch. I guess the key word here is "most," though.
Hmmm...

        -Mike Pelletier.
Received on Mon Sep 15 1997 - 08:22:48 MDT