>>> [EMAIL PROTECTED] 07/26/00 06:38PM >>>

>But with the httpd.conf MaxRequestsPerChild parameter available to force
>any and all memory leaks back to ground zero periodically, how bad *is*
>this memory leak, compared to the number of people who find they can
>no longer rotate their production server logs at modssl 2.6.5?
In this case, it would be a memory leak in the parent, not in the child, since the problem happens when the server is shutting down and restarting.  So having the children die off doesn't do any good because the new children get spawned with an image of the parent, leaked memory and all.  Restart the server enough times, and your parent process gets to be pretty big in memory (and therefore its children do, too).
 
--Cliff

Reply via email to