On Sat, 10 Jun 2000, you wrote:
> On Sat, Jun 10, 2000 at 01:04:49AM +0800, Ian C.Sison wrote:
> > Hi all,
> >
> > I've tried working with the apache-php3perl SRPM which was posted on the
>
> snip
>
> > Starting httpd: Syntax error on line 862 of /etc/httpd/conf/httpd.conf:
> > Invalid command 'PerlHandler', perhaps mis-spelled or defined by a module
> > not included in the server configuration
> >
> > Now i know the FAQ entries on this error code, but i know perl is included and
> > linked statically, so the keyword PerlHandler should work. Looking at httpd -l
> > I get:
> >
> > Compiled-in modules:
> > http_core.c
> > mod_so.c
> > mod_perl.c
> > mod_php3.c
> > suexec: enabled; valid wrapper /usr/sbin/suexec
> >
> >
>
> snip
>
>
>
> IIRC from the mod_perl docs, mod_action.c is the only one that HAS to be in there
> for mod_perl... add that and see.
LoadModule action_module modules/mod_actions.so
AddModule mod_actions.c
I've checked and they are both in my httpd.conf.
Still no resultion to this.
I tend to believe that this is not a problem due to the fact that i built this
from an SRPM. I think it's a bug in apache or mod_perl that probably hasn't
been discovered yet. It's clear from httpd -l that mod_perl.c is included, so
why does not it recognize the Perl configuration phrases/words?
Anyone else with some ideas?
-------------------------------------------------------
