benoit wrote:
Ok, now I'm ashamed.
After some more RTFM, I found that there was a missing-closing-parens
festival going on in my configuration file...
So, for the record and/or those who will find this message some
debugging day :
I followed the suggestion of Pratical Mod_perl, p.132 : I've added a a
#!/usr/bin/perl
and
__END__ in my <perl> block.
Then, I ran my configuration file with regular Perl :
$ cd [in my apache server root]
$ perl -cx conf/httpd.conf
And Perl informed me a bit more about my stupidity.
From Changes:
=item 1.21_03 - March 15, 2000
new variable $Apache::Server::StrictPerlSections, if true, will croak
<Perl> section generates invalid Apache configuration syntax
Does it do the trick? I'm not sure why it's not documented.
Anyway, I would like to mention that this would be really, really great
if this kind of error would show up somewhere, at least when one is
running in "Debug-mode" like I did... Is it something that is present in
mod_perl v2 (from my readings, I would say No)? If not, could it be?
In mp2 <Perl> sections errors are fatal by default (will be shortly)
--
__________________________________________________________________
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
--
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html