Perrin Harkins wrote:
>>Does using the Apache::GTopLimit module have the same net effect as
>>restarting the server itself by simply killing off the actual
> 
> processes
> 
>>which are growing beyond the set threshold, and thereby causing new
>>processes to be born?
> 
> 
> It does kill off processes that are getting too big, and you definitely
> should use either GtopLimit or SizeLimit to get the most out of your
> server.  However, it's not quite the same thing as a restart.  Over
> time, some of the shared memory from the parent process appears to
> become unshared, and new processes that are spawned start out with less
> shared memory because of this.  

Hmm, when a new process starts it shares *everything* with the parent. 
Why do you say that it's not?

It doesn't matter if the process gets killed because of 
MaxRequestPerChild or FooLimit thresholds.

__________________________________________________________________
Stas Bekman            JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/     mod_perl Guide ---> http://perl.apache.org
mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org   http://ticketmaster.com

Reply via email to