the apache-1.3.29-r1 init-script (/etc/init.d/apache) contains: env -i PATH=$PATH /sbin.... in start(). this clears the variable PERL5LIB from the environment which may be needed if you have perl-modules located at a special location. If you then run scripts under mod_perl that use these modules apache will complain about not finding these modules. if you change the above line to: env -i PATH=$PATH PERL5LIB=$PERL5LIB /sbin... everything works fine Reproducible: Always Steps to Reproduce: 1. try to preload a module NOT located in the standard @INC in commonapache.conf 2. restart apache 3. Actual Results: mod_perl not finding modules in PERL5LIB Expected Results: @INC should have contained the dirs in PERL5LIB
Even better: when /etc/init.d/apache ist started when starting / rebooting a machine this env-variable is not yet set (I introduced it via. the /etc/env.d structure). So mod-perl scripts fail when requested after a reboot but when I (root) does a /etc/init.d/apache restart all works well. So maybe an additional variable in /etc/conf.d/apache where the admin could enter a path passed to apache as PERL5LIB could be entererd would solve this.
In cvs, thanks for the bug report.