On Wed, 2007-02-14 at 14:57 +0000, Carl Johnstone wrote: > Hi, > > I'm moving to mod_perl2 and looking at the new startup where perl can be > loaded either pre-config or postconfig. I've been trying both options. > > If I start perl pre-config, I'm getting output from the perl stuff to the > screen as well as the error log. It's also fairly slow and runs even if > you're issuing a stop command. > > If I start perl post-config, everything is an awful lot quicker. However > configtest doesn't load perl, and therefore doesn't fail if perl is unable > to start (for example if a module is missing). > > I'd like to have something in the middle, ideally with perl starting > post-config with "apachectl configtest" also checking that perl can start. > As far as I can see from the docs that isn't an option. > > Am I missing anything, or has anybody got any suggestions?
Not that I can figure out. What I ended up doing was changing my apachectl file to set an environment variable when I was stopping apache, which signalled to my code that it shouldn't try to load everything. You also have the option of avoiding loading everything on the first start (because apache starts, and then immediately restarts, just to check that it can). But then there is no STDOUT, so you don't get immediate feedback about any failures. If anybody has any better ideas, i'd love to hear them Clint
