> That won't be enough in all cases unless it actually replaces the
> interpreter, like PerlFreshRestart used to.
>
> I would do a graceful shutdown and restart.
I've had lots of problems with graceful restarts hanging indefinitely, I
think caused by issues with the mod_ssl module.
I'd also rec
On Tue, Jul 14, 2009 at 3:25 PM, Philippe M.
Chiasson wrote:
>> Graceful restart used to just re-read the
>> conf, not restart the perl interpreter.
>
> Now I believe it does, and it's easy to verify.
>
> A loaded PerlModule will get reloaded on graceful restart, that's for sure.
That won't be eno
On 14/07/09 15:00 , Perrin Harkins wrote:
> On Tue, Jul 14, 2009 at 2:36 PM, Philippe M.
> Chiasson wrote:
>> On a gracefull restart, all perl interpreters are shutdown and new,
>> clean ones replace them, reloading any module you configure for preloading.
>
> I don't think this is right, Philippe
On Tue, Jul 14, 2009 at 2:36 PM, Philippe M.
Chiasson wrote:
> On a gracefull restart, all perl interpreters are shutdown and new,
> clean ones replace them, reloading any module you configure for preloading.
I don't think this is right, Philippe, unless something has changed
with it in mod_perl 2
On 14/07/09 14:04 , E R wrote:
> Hi,
>
> I was wondering how graceful restarts of apache interact with modperl
> and "pre-loaded" modules.
>
> Specifically, if the apache parent process loads module Foo.pm, and I
> modify Foo.pm, can I use a graceful restart to get the apache parent
> to read the
Hi,
I was wondering how graceful restarts of apache interact with modperl
and "pre-loaded" modules.
Specifically, if the apache parent process loads module Foo.pm, and I
modify Foo.pm, can I use a graceful restart to get the apache parent
to read the new version of Foo.pm?
Thanks,
ER
