Jim Gottlieb wrote: > Hi. I've just upgraded from mod_perl 1.27 to 2.02 as part of upgrading > to Apache 2. > > The main problem I'm having with our mod_perl script is its notion of > the current directory as it relates to finding add-on modules. > > We call the script as http://dom.ain/perl-bin/subdir/scriptname and we have > the > include modules it needs in /perl-bin/subdir and that worked fine > before we upgraded. > > But now it won't find the modules unless we put them (or symlink them) > one level up in /perl-bin/. We'd rather have all the script-specific > .pm files located in the same directory as the script, and not clutter > the main /perl-bin directory.
the current working directory isn't a thread-safe proprety, and since apache-2.0 can now be threaded, mod_perl-2.x takes the safe path and doesn't change directory for you. See http://thread.gmane.org/gmane.comp.apache.mod-perl/20311 and ModPerl::RegistryPrefork as possible solutions. -------------------------------------------------------------------------------- Philippe M. Chiasson m/gozer\@(apache|cpan|ectoplasm)\.org/ GPG KeyID : 88C3A5A5 http://gozer.ectoplasm.org/ F9BF E0C2 480E 7680 1AE5 3631 CB32 A107 88C3A5A5
signature.asc
Description: OpenPGP digital signature
