On Tue, Jul 13, 2010 at 12:33 AM, Matty Ronald <matty.rnld@xxxxxxxxx> 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 replace a child that exits due to MaxRequestsPerChild, if you're not below MinSpareThreads. > When and how does the parent pid get notified that it is time for the > child to die because MaxRequestsPerChild has been reached? The child offs itself, and the parent both checks every second to see if a child has exited and knows which indvidual threads are still running and which have exited, so it can keep track of Min/Max SpareThreads. > 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? All the bookeeping is in the child. The parent only tells the child it's time to exit for MaxSpareThreads (children can't figure that out on their own) and restarts. -- Eric Covener covener@xxxxxxxxx --------------------------------------------------------------------- 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
|