Why don't you just set your maximum child requests to a reasonable number and have them restart themselves after they have executed what you would call "enough requests to need flushing".
Ric. ----- Original Message ----- From: "Jim Morrison [Mailinglists]" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, May 17, 2002 3:24 PM Subject: modperl idle timeout.... > Guys, > > I am currently using mod_perl & XML::Xalan.. which is going well.. (For > those of you who answered questions of mine about memory usage, I found some > big memory leaks in my code... Doh!... Much better now... ) > > However, because it's only a little box, and because Xalan (and therefore > mod_perl) is not used 24x7 I have set up and apache graceful restart on a > crontab, so that mod_perl gets flushed out of use every hour... which keeps > our mem usage down, and stops me having lots of big "httpd"'s lying around > that don't need to have Perl compiled into them.. > > Anyhow... I was wondering... is there a simple way to set up a sort of > "idle timeout" to get each single httpd to restart itself if two conditions > are met: > - 1 - It has compiled mod_perl > - 2 - The mod_perl aliases have not been accessed for 'x' minutes... > > What do you guys recon... is crontabbing a restart easier.. is it ill > advised? (Ofcourse the restart runs even when you are using mod_perl.. > which doesn't really help anyone.. cos then it has to go through the restart > lag.. ) > > > Oh well... would love to hear your thoughts, > > All the best, > > > Jimbo > > > > Jim Morrison > _____________________________ > Technology & Development Partner > Isotope LLP > 9, 2 Laura Place > Bath, Somerset > United Kingdom >
