really, there is no trustworthy way to do what you want except by stopping
and starting the server.
During development, you can use either the PerlFreshRestart directive or
Apache::StatINC. I typically avoid PerlFreshRestart due to the demons, but
Apache::StatINC is rather handy, although it occasionally misbehaves on
me...
there's an entire section of the guide devoted to this:
http://perl.apache.org/guide/porting.html#Reloading_Modules_and_Required_F
HTH
--Geoff
> -----Original Message-----
> From: Mark Hewis [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, June 21, 2000 8:38 AM
> To: [EMAIL PROTECTED]
> Subject: Restarting a modperl server
>
>
> What is the best way to restart modperl server that
> a) Reloads all perl modules
> b) reloads and runs the configuration file
>
> and if possible
>
> c) Only kills each child after it has finished its request
>
>
> 'kill -USR1 pid' doesn't reload the perl-modules in my test
>
> neither does
>
> 'kill -HUP pid'
>
> I am starting all the modules with a startup.pl script called in the
> httpd.conf file
>
> Any ideas
>
> Thanks
>
> Mark
>
>
>
> This e-mail, and any attachment, is confidential. If you have
> received it in error, please delete it from your system, do
> not use or disclose the information in any way, and notify me
> immediately. The contents of this message may contain
> personal views which are not the views of the BBC, unless
> specifically stated..
>
