On Sun 10 Feb 2008, James Breat wrote: > to resolve handler `ModPerl::Registry': Can't locate > ModPerl/Registry.pm in @INC (@INC contains: > /usr/lib/perl5/5.8.8/i486-linux-thread-multi /usr/lib/perl5/5.8.8 > /usr/lib/perl5/site_perl/5.8.8/i486-linux-thread-multi > /usr/lib/perl5/site_perl/5.8.8 /usr/lib/perl5/site_perl . > /usr/local/srv/apache2) at (eval 2) line 3.\n" > > locate Registry.pm returns: > /usr/lib/perl5/site_perl/5.8.8/i486-linux-thread-multi/ModPerl/Registry.pm
I don't think that is true for your new root. So either copy all needed modules to it or load them *before* the chroot call. AFAIK mod_chroot installs a PostConfig handler at APR_HOOK_REALLY_LAST+10, that means really_really_last. Anything before that runs in the original root and hence can load modules, see http://perl.apache.org/docs/2.0/user/handlers/server.html#Server_Life_Cycle Torsten
