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.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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@xxxxxxxxxxxxxxxx
   "   from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx



[Index of Archives]     [Open SSH Users]     [Linux ACPI]     [Linux Kernel]     [Linux Laptop]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Squid]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]

  Powered by Linux