Re: PerlConfigRequire and die [solved]

2009-02-28 Thread Clinton Gormley
On Mon, 2009-02-23 at 15:32 +0100, Clinton Gormley wrote: > Hiya > > I'm using PerlConfigRequire to load my Perl application, which also sets > up the VirtualHost's using $r->add_config() > > The problem is, if one my modules has a compile time error, instead of > getting the real error message,

Re: PerlConfigRequire and die

2009-02-28 Thread Torsten Foertsch
On Thu 26 Feb 2009, Clinton Gormley wrote: > > Why don't you do that in a block? > > How is this different from doing it in the startup.pl file?   Yes, I see, the 2nd run of the code doesn't have STDERR either. So, you can open a startup logfile in perl and override CORE::GLOBAL::warn/die or i

Re: PerlConfigRequire and die

2009-02-26 Thread Clinton Gormley
> > eval { load_application();1} > > || do { > > warn $@; > > force_apache_to_quit_startup_once_stderr_flushed(); > > } > > Why don't you do that in a block? How is this different from doing it in the startup.pl file? > > Be aware that this code is executed twice at

Re: PerlConfigRequire and die

2009-02-26 Thread Torsten Foertsch
On Thu 26 Feb 2009, Clinton Gormley wrote: > > > Is there any way I can: > > >  - cause the error to be reported properly > > >  - force apache not to start > > > >  eval {load_application(); 1} || do { warn $@; die }; > > Unfortunately, no.  That still just dies with the obscure error > message. I

Re: PerlConfigRequire and die

2009-02-26 Thread Clinton Gormley
> > > > Is there any way I can: > > - cause the error to be reported properly > > - force apache not to start > eval {load_application(); 1} || do { warn $@; die }; Unfortunately, no. That still just dies with the obscure error message. It seems that STDERR only gets flushed in a later stage

Re: PerlConfigRequire and die

2009-02-23 Thread Mark Hedges
On Mon, 23 Feb 2009, Clinton Gormley wrote: > to: >eval {load_application(); 1} || print STDERR $@; >1; > > then I see the proper error message, but apache starts > anyway. > > Is there any way I can: > - cause the error to be reported properly > - force apache not to start eval {load

PerlConfigRequire and die

2009-02-23 Thread Clinton Gormley
Hiya I'm using PerlConfigRequire to load my Perl application, which also sets up the VirtualHost's using $r->add_config() The problem is, if one my modules has a compile time error, instead of getting the real error message, I get something like this: