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.
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?
For everyone that did read my messages, thanks! :)
benoit wrote:
Hello.
I'm trying to build an Apache configuration that makes it possible for all the developpers in my group to work with their own Apache process. For doing so, I'm using <perl> sections that build the server configuration; changing the User/Group, dynamically ajusting the DocumentRoot and Port, etc.
But however I try to do it, I just can't make it work. It's acting the same as if the perl sections where not taking in account when starting the server. But mod_perl is working, and it's seems to at least try to execute the directives : if I start it with debug trace, I got that :
- - - -8<- - - -
[EMAIL PROTECTED] apache]$ MOD_PERL_TRACE=all ./bin/httpd -f /home/bcaron/apache/conf/httpd.conf -X
perl_parse args: '/dev/null' ...allocating perl interpreter...ok
constructing perl interpreter...ok
loading perl module 'DynaLoader'...ok
ok
running perl interpreter...ok
mod_perl: 0 END blocks encountered during server startup
loading perl module 'Apache'...loading perl module 'Apache::Constants::Exports'...ok
ok
loading perl module 'Tie::IxHash'...not ok
perl_section: </VirtualHost>
perl_section: </Directory>
perl_section: </Files>
perl_section: </Directory>
perl_section: </Files>
[EMAIL PROTECTED]' directive is ITERATE, (0 elements)
default: iterating over @DirectoryIndex
perl_section: </Location>
[EMAIL PROTECTED]' directive is ITERATE, (0 elements)
default: iterating over @PerlModule
perl_section: </Location>
- - - -8<- - - -
If I try to start the server with a <perl> section only, it simply does not work ; the server try to start on the default port 80 and since it needs to work as a normal user, it stops there. I added :
ServerType "standalone" ServerRoot "/home/bcaron/apache" Port 9000
To make it start on the Port 9000 and to make sur it use my local build in my $HOME.
I'm working with mod_perl 1.29 and Apache 1.3.31. I compiled mod_perl and Apache like this :
perl Makefile.PL APACHE_SRC=../apache_1.3.31/src/ DO_HTTPD=1 USE_APACI=1 EVERYTHING=1 ADD_MODULE=proxy,rewrite APACHE_PREFIX=/home/bcaron/apache PERL_TRACE=1 MOD_PERL_PREFIX=/home/bcaron/mod_perl
Any idea what I'm doing wrong? I once did a configuration that did something like it, but the server was started "root" with sudo, and I would prefer not to do this now...
Thanks for any help
Benoit
-- 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
