Re: global variables and reparsing (short reproducible example)

[Marc Lehmann]

On Wed, May 24, 2000 at 11:30:40AM -0700, Perrin Harkins <[EMAIL PROTECTED]> wrote:
> > example did something similar, indeed, but it had to be embedded into the
> > module source, which is somewhat inconvinient.
> 
> If you don't have PerlFreshRestart turned on (it is not recommended on
> production servers), only the stuff in your config file (<Perl> sections
> and PerlModule/PerlRequire) gets called twice.  You can block things out
> like this:

Actually, and to my surprise, PerlModule/PerlRequire is not done twice,
at leats not with respect to reparsing. They simply don't reparse the
modules, so mod_perl works *perfectly* without PerlFreshRestart, and
without special measures.

> SUGUSR1.  Personally, I always do cold stop and start on my production
> servers, in order to maximize shared memory, but this is difficult when
> you don't have a load-balanced cluster at your disposal...

*) It's also more disruptive ;)

-- 
      -----==-                                             |
      ----==-- _                                           |
      ---==---(_)__  __ ____  __       Marc Lehmann      +--
      --==---/ / _ \/ // /\ \/ /       [EMAIL PROTECTED] |e|
      -=====/_/_//_/\_,_/ /_/\_\       XX11-RIPE         --+
    The choice of a GNU generation                       |
                                                         |