You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@httpd.apache.org by Matty Ronald <ma...@gmail.com> on 2010/07/13 06:48:50 UTC

[users@httpd] In Apache 2.2.x 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.

Hi All,

Can anyone help me in Apache 2.2.x 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 MaxRequestsPerChild has been reached?

Does the child send back to the parent that it is servicing it's last
client BEFORE it starts doing so or does the parent in some way keep
track of how many clients the child has serviced or what?




Thanks
Matty.

---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org