justin wrote: [...]
SB> Second, you could write a similar to Apache::SizeLimit handler module, which SB> will determine when to terminate the process, but the problem is that you need SB> to reload the parent server anyway if you don't rely on Apache::Reload.
Penny drops -- I can do this in my own exit handler, no? where I am doing housekeeping, and possible child termination anyway. I could even syntax check the new code to stop corrupt files or *cough* programmer mistakes.
Of course.
Since I'm still using Registry, I'd disable its checking of
file timestamps.
Oops, sorry, I've completely forgotten that Apache::Registry does this reloading. You can use Apache::RegistryBB which doesn't do that or write another subclass as you have suggested. So yes, it's relevant that you are using Registry.
> But why do I need to worry about the parent server, if > the parent server has a fixed code base (a fixed set of library use's in > startup.pl and not the "code" as such)?
I've assumed that you preload everything at the server startup (You did know that you can preload registry scripts [1], to improve memory sharing, didn't you?) in which case the parent server which contains the preloaded data will still keep the old code and new child process will "inherit" this old code. Of course if you don't preload scripts, than you are fine.
1) http://perl.apache.org/docs/1.0/guide/performance.html#Preloading_Registry_Scripts_at_Server_Startup http://perl.apache.org/search/swish.cgi?query=Apache%3A%3ARegistryLoader&sbm=&submit=search
__________________________________________________________________ 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
-- Reporting bugs: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html
