On Tue, Jan 25, 2011 at 2:44 AM, Andrew Punch
wrote:
> Hi,
>
> Thanks for the quick response. I notice that you have added a comment in bug
> 41743 saying it is a bug in prefork that does not affect worker. You have
> also stated that it is fixed in trunk.
>
> I have run a test using 2.3.10 alpha
Hi,
Thanks for the quick response. I notice that you have added a comment in
bug 41743 saying it is a bug in prefork that does not affect worker. You
have also stated that it is fixed in trunk.
I have run a test using 2.3.10 alpha - the prefork still has the issue
and the worker does not have the
On Mon, Jan 24, 2011 at 8:17 PM, Andrew Punch
wrote:
> Hi,
>
> During the week I hit the situation described in 41743. A child process
> is connected to a client using a keepalive connection. A graceful
> restart (SIGUSR1) is issued. If the MaxKeepAliveRequests is high and the
> client is chatty t
Hi,
During the week I hit the situation described in 41743. A child process
is connected to a client using a keepalive connection. A graceful
restart (SIGUSR1) is issued. If the MaxKeepAliveRequests is high and the
client is chatty the child process will not exit until the client
disconnects.
Thi
