OK,
i'm not a mod_perl hacker, but i've installed a Apache2 + mod_perl2
under a FreeBSD VMWare to test, i used the same mod_perl2
configuration...... same script! I copy paste this config in the
global server config or default vhost:
#
####
PerlModule ModPerl::PerlRun
Alias /perl-run/ /usr/local/www/perl/
<Location /perl-run>
SetHandler perl-script
PerlResponseHandler ModPerl::PerlRun
PerlOptions +ParseHeaders
Options +ExecCGI
</Location>
as you can see, it's very basic! It works on FreeBSD not under Debian
Sarge.... the same error,
[Mon Feb 21 21:27:41 2005] [error] /usr/local/www/perl/test.pl not
found or unable to stat
and when i do a 'cat /usr/local/www/perl/test.pl' the file exists,
executable, etc...... everything is OK, if it runs under
Registry.......
but check out my different HEAD output
FreeBSD :
Server: Apache/2.0.53 (FreeBSD) mod_perl/1.999.20 Perl/v5.8.6
Debian:
Server: Apache/2.0.52 (Debian GNU/Linux) mod_perl/1.999.20 Perl/v5.8.4
Can the perl version change anything? can the apache version change anything?
I can post all my debian apache 2 config files......... if it's necessary
or with you Stas, i can jump into debuging like the way you talked in
the last post...
i'm on this problem for days ago...
thanks in advance
Bruno
On Mon, 21 Feb 2005 20:49:57 -0500, Stas Bekman <[EMAIL PROTECTED]> wrote:
> Bruno Lavoie wrote:
> > Hello,
> >
> > my problem is very confusing! and i absolutely need it working!
> > at work i need to configure multiples developement zone under apache 2
> > and mod_perl 2, and this as virtual host for each programmer. I need
> > to run environement in ModPerl::PerlRun because we have dirty scripts
> > that doesnt work under ModPerl::Registry
> [...]
> > the weirdest thing is the PerlResponseHandler ModPerl::PerlRun in the
> > <Files ~ ...> directives scope dont call scripts, my error log show me
> > when i call a .pl file :
> > Code:
> >
> > [Thu Feb 17 10:02:55 2005] [error] /fsg/intranet-fsgbla/htdocs/test.pl
> > not found or unable to stat
>
> Where is the script physically located? At the above path? Is it
> executable and readable (I suppose so, since registry works). Also you
> could try to enable debugging in the RegistryCooker.pm and see whether it
> runs. at the end it's easy to compare Registry.pm with PerlRun.pm and try
> to see what difference creates the problem. I'd guess that this difference
> is the crucial one:
>
> PerlRun.pm flush_namespace => 'flush_namespace_normal',
> Registry.pm flush_namespace => 'NOP',
>
> the actual functions are in RegistryCooker.pm.
>
> --
> __________________________________________________________________
> Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
> http://stason.org/ mod_perl Guide ---> http://perl.apache.org
> mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com
> http://modperlbook.org http://apache.org http://ticketmaster.com
>
