Does this cause significant performance degradation?
If anything, this would cause a performance increase as the chdir
function is now a no-op.
And you are not doing a system call to chdir
On 2006-01-20 at 17:59, Philippe M. Chiasson ([EMAIL PROTECTED]) wrote:
> the current working directory isn't a thread-safe property, and since
> apache-2.0
> can now be threaded, mod_perl-2.x takes the safe path and doesn't change
> directory
> for you.
That makes sense.
> ModPerl::RegistryP
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
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
