Re: [squid-users] read_timeout

On 06/27/2014 07:56 AM, Jeremy Hustache wrote:

> OK, if i understand a negative read_timeout value reset global structure
> of timeout.
>
> So, is a 0 value for read_timeout token in squid conf file means no
> timeout ?

I did not check Squid2 sources, but AFAICT, Squid3 does not treat a zero
read_timeout value specially, and I doubt it should. Squid should check
for overflows instead, but does not (yet?).

If you want a large read_timeout, use a large value. For example, two
years should be large enough for virtually all practical purposes and
small enough to prevent (current time + timeout) overflows in the
foreseeable future.

Please note that large timeouts create "stuck" connections in most
deployment environments, and those stuck connections not only consume
file descriptors but may eat 10s of MBs of RAM in environments where
Squid opens SSL connections to servers.

HTH,

Alex.

> On 06/27/14 14:43, Jeremy Hustache wrote:
>> Hello,
>>
>> Is it possible to set read_timeout value to a negative value in order
>> to have infinite timeout on this event ?
>>
>> I use "Squid Cache: Version 2.7.STABLE9", I try to set read_timeout to
>> -1 but I have some assert in commSetTimeout() which crash squid daemon.
>>
>> Thanks
>>
>>
Received on Fri Jun 27 2014 - 15:22:01 MDT