Kent, Mr. John wrote: > Greetings, > > Have noticed that modperl-2.0 servers running on Solaris 2.7 start > off at 23M in size. Five hours later they were at 38M. If allowed to > continue > they could eventually use up all available RAM and crash the system. > > Stopping then restarting returned them to 23M. > > Has anyone else encountered this and is there a recommended solution > other than periodically stopping and starting?
Are you using the prefork mpm or a threaded one? If this is a prefork, use Apache::SizeLimit (or Apache::GTopLimit) just like in 1.0. See: http://perl.apache.org/release/docs/1.0/guide/performance.html#Preventing_Your_Processes_from_Growing If you are talking about threaded mpms, we will need to develop new tools to restrict the size of the perl interpreters in the pool. Other than try to figure out if your code (or the server) doesn't leak. __________________________________________________________________ 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