On Tue, August 3, 2010 13:59, Matty Ronald wrote:
> Hi,
>
> Parent httpd process isn't spawning a new replacement child in a timely
> fashion,
> after MaxRequestsPerChild has been hit and the child worker httpd has
> exited with the below settings:
>
> Timeout 70
> KeepAlive On
> KeepAliveTimeout 6
Hi,
Parent httpd process isn't spawning a new replacement child in a timely fashion,
after MaxRequestsPerChild has been hit and the child worker httpd has
exited with the below settings:
Timeout 70
KeepAlive On
KeepAliveTimeout 60
StartServers 2
MaxClients 150
MinS
On Tue, Jul 13, 2010 at 12:33 AM, Matty Ronald wrote:
> Hi All,
>
> Can anyone help me Why parent httpd process isn't spawning a new
> replacement child in a timely fashion, after MaxRequestsPerChild has
> been hit and the child worker httpd has exited.
>
The parent doesn't necessarily have to re
Hi All,
Can anyone help me Why parent httpd process isn't spawning a new
replacement child in a timely fashion, after MaxRequestsPerChild has
been hit and the child worker httpd has exited.
When and how does the parent pid get notified that it is time for the
child to die because MaxRequestsPerCh