Re: filedescriptor leak on 1.2b20

On Sat, 16 May 1998, Henrik Nordstrom wrote:

> Apiset Tananchai wrote:
>
> > My problem is that squid start using a large number of file
> > descriptors when user trying to goto ip addresses that have no
> > route to. Here's some part of file descriptor report from
> > cache_object://.../filedescriptors 203.155.33.12 is our proxy
> > server and 203.155.32.150 is the host that has to route to it.
>
> This probably caused by a known issue in 1.2beta. The caused is client
> half-side close support, and the workaround is to disable TCP half-side
> close support. [patch attached]
>
> Squid can't detect if is only half-closed request or aborted, and
> because of this it has to assume that it is half-closed. This is
> normally not a problem as the requests times-out after the connect
> timeout interval, but when a popular server goes dead it may become a
> big problem.
>
> If this is the cause, then you should see a fair amount of
> filedescriptors marked as "half-closed" as well. If not please send a
> message to squid-bugs@nlanr.net.

Maybe this is not the cause, I only see around 15-20 filedescriptors
marked as 'half-closed' while >2000 descriptors were used by connections
to no route host. BTW, I'll try to apply your patch and let you know if it
fix the problem.

Thanks for your help,

--
aet