Hi Elizabeth, Apache::Reload or Apache::StatINC can reload modules for you without needing to restart the server. Your provider would need to have one of these installed and set up in the httpd.conf. If you get a choice in which one you use, Apache::Reload is much more configurable so you have more control over what gets reloaded when. Apache::StatINC will simply reload any module as soon as it's changed.
more details: http://perl.apache.org/guide/porting.html#Reloading_Modules_and_Required_F --Carolyn On Thu, Apr 04, 2002 at 10:20:37PM -0600, Elizabeth Barham wrote: > Hi, > > I have been writing scripts on a local machine. I noticed that > mod_perl can tell when I change a CGI script, but if that script > accesses a module or module that changes, it often times does not > notice this. So, when I update the module files I restart apache. > > This has worked fine for my local machine, but the day is drawing near > in which I may be installing this onto a web-host provider running > mod_perl. If this happens and there is an upgrade or a bug-fix in a > module, how does one deal with it? > > Does mod_perl garbage collect the compiled code after it has not been > accessed in a while? > > Thank you, Elizabeth
