in reply to Apache/mod_perl configuration

In short: yes it does. You can test it by having the perl script write output to a file. When you restart the server, you will find that the file is written.

Edit: according to perrin, it doesn't.

Replies are listed 'Best First'.
Re^2: Apache/mod_perl configuration
by perrin (Chancellor) on Dec 01, 2004 at 15:14 UTC
    No, it does not. That module will not be loaded until the location is requested. To load it at startup, you would have to call it with a PerlModule or PerlRequire or load it from startup.pl.
[reply]
Re^2: Apache/mod_perl configuration
by Mutant (Priest) on Dec 01, 2004 at 13:04 UTC
    Is there some way to prevent this happening? I assume this occurs accross other containers (such as VirtualHost)?
[reply]
      It does happen across other containers too yes. I assume you cannot prevent this because it's what mod_perl does: load the thing into memory to be ready when someone makes a request.
[reply]
        I see... makes sense.... thanks.
[reply]

      (I'm taking Jaap's answer at face value. I don't remember much about mod_perl.)

      What are you trying to accomplish? There might be other ways of accomplishing what you want to accomplish. One thing you could do is to have a barebones handler that loads up the full module and calls it:

      sub handler {
   require Full::Module;
   goto(&Full::Module::handler);
}

      [download]

      (You might have to fool with the args in @_ a little. I don't remember what args a handler receives.)

      Of course, once the module is loaded, it will stay loaded.

[reply]
[d/l]

In Section Seekers of Perl Wisdom