Philippe M. Chiasson wrote on 03.08.2005:
>Jan Eden wrote:
>>[...] SetHandler perl-script PerlResponseHandler
>>ModPerl::RegistryPreFork
>
>Case sensitivity issue here it's
>ModPerl::RegistryPerfork, lower case f
If this is not embarrassing, nothing is.
Thanks!
- Jan
-
Jan Eden wrote:
> Philip M. Gollucci wrote on 01.08.2005:
>>>Jan Eden schrieb:
>> [...]
>>
>>As it will say, use
>>
>>ModPerl::RegistryPrefork or ModPerl::PerlRunPrefork.
>>
> Thanks for the hint - but Apache fails to resolve the handler, although
> ModPerl::RegistryPreFork is right there:
>
> [W
Philip M. Gollucci wrote on 01.08.2005:
>>Jan Eden schrieb:
>>
>>>Hi,
>>>
>>>I just noticed that the working directory for scripts executed via
>>>a mod_perl handler is /.
>>>
>>>Is there a way to change that? Some of the scripts I use rely on
>>>the directory they are stored in is the current wor
Jan Eden schrieb:
Hi,
I just noticed that the working directory for scripts executed via a mod_perl
handler is /.
Is there a way to change that? Some of the scripts I use rely on the directory
they are stored in is the current working directory.
http://perl.apache.org/docs/2.0/user/porting/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
In Apache 1.3 this has been done by mp automatically when executing
under PerlRun or Registry but because of the oulined problems this is
not possible any more at least when supporting all mpms.
If you are running on prefork and your cgi must be able
Hi Tom,
Tom Schindl wrote on 01.08.2005:
>-BEGIN PGP SIGNED MESSAGE- Hash: SHA1
>
>If you are running mp2 that's true simply because of the fact that
>chdir in perl is not thread-safe :-(
>
>If you are running in prefork(which is only available on *nix) you
>could chdir yourself at the to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
If you are running mp2 that's true simply because of the fact that chdir
in perl is not thread-safe :-(
If you are running in prefork(which is only available on *nix) you could
chdir yourself at the top of your handler.
Tom
Jan Eden schrieb:
> Hi,
>
