Re: Getting a non-zero error code from httpd(1) if the application doesn't compile

2011-10-16 Thread Torsten Förtsch
On Sunday, 16 October 2011 02:26:53 Ævar Arnfjörð Bjarmason wrote: > > $ cat xx > > > > use POSIX(); > > POSIX::exit(15); > > > > $ httpd -c 'Include "'$PWD/xx'"'; echo $? > > 15 > > $ cat xx > > > > die > > > > $ httpd -c 'Include "'$PWD/xx'"'; echo $? > > Syntax error on line 2 of /.../xx: >

Re: Getting a non-zero error code from httpd(1) if the application doesn't compile

2011-10-15 Thread Ævar Arnfjörð Bjarmason
On Sat, Oct 15, 2011 at 19:35, Torsten Förtsch wrote: > On Saturday, 15 October 2011 18:00:26 Ævar Arnfjörð Bjarmason wrote: >> Maybe this is something elementary that I've just missed, but it seems >> to me that when transitioning from mod_perl 1 to 2 there's no way to >> get a non-zero exit code

Re: Getting a non-zero error code from httpd(1) if the application doesn't compile

2011-10-15 Thread Torsten Förtsch
On Saturday, 15 October 2011 18:00:26 Ævar Arnfjörð Bjarmason wrote: > Maybe this is something elementary that I've just missed, but it seems > to me that when transitioning from mod_perl 1 to 2 there's no way to > get a non-zero exit code from Apache if your application has > compilation errors. >

Getting a non-zero error code from httpd(1) if the application doesn't compile

2011-10-15 Thread Ævar Arnfjörð Bjarmason
Maybe this is something elementary that I've just missed, but it seems to me that when transitioning from mod_perl 1 to 2 there's no way to get a non-zero exit code from Apache if your application has compilation errors. I have an application that I'm loading like this: PerlPostConfigRequire