Under mod_perl I use "PerlLoadModule Foo" in the Apache config file to load the Catalyst app "Foo".<div><br></div><div>At one point in time it was common with mod_perl to preload modules using a "<a href="http://startup.pl">startup.pl</a>" file. The idea, IIRC, was to preload modules in the parent so they are shared when the parent Apache process forks. I'm wondering if there is any benefit to this when running a Catalyst app.</div>
<div><br></div><div>If I look at the parent Apache process (the one owned by "root") using lsof I see all the .so files for Perl modules my app uses (that have binary components), so that would indicate to me that modules are indeed loaded into the parent. And if I add "warn owner $< and $>\n" to modules it will show UID 0, for the root user upon Apache start.</div>
<div><br></div><div>So, is there any reason to use <a href="http://startup.pl">startup.pl</a> to "preload" modules with mod_perl and Catalyst?</div><div><br></div><div><div><br></div>-- <br>Bill Moseley<br><a href="mailto:moseley@hank.org" target="_blank">moseley@hank.org</a><br>
</div>