On 4/26/06, Henrik Nordstrom <[EMAIL PROTECTED]> wrote:
> ons 2006-04-26 klockan 11:13 -0300 skrev Gonzalo Arana:
>
> > I proposed min_alive to limit helper recycle rate, not to increase it.
>
> I know, and I question the need to have this lower limit on the helper
> restarts.
>
> > max_requests im
ons 2006-04-26 klockan 11:13 -0300 skrev Gonzalo Arana:
> I proposed min_alive to limit helper recycle rate, not to increase it.
I know, and I question the need to have this lower limit on the helper
restarts.
> max_requests imposes a relation between request rate and helper
> recycle rate. If
> <..snip.. max_requests>
>
> > o min_alive: to avoid short-lived helpers, they should stay alive at
> > least for this amount of seconds. This should help against
> > fork-query-kill per request behaviour if request rate is drastically
> > increased.
>
> Not sure about this one. If you have probl
ons 2006-04-26 klockan 07:40 -0300 skrev Gonzalo Arana:
> o max_requests: after this number or requests, the helper will be
> shutdown and replaced by a new one. This is to help leaky helpers.
Makes sense. Today the helpers are restarted at log rotation (needed as
their stderr is connected to ca
I am using external_acl extensively in my production servers, and I
think it would be nice to add external_acl these flags:
o max_requests: after this number or requests, the helper will be
shutdown and replaced by a new one. This is to help leaky helpers.
o min_alive: to avoid short-lived helpe
