When I edit tht httpd.cong for mod_perl,
Apache not works.
?
Sandhya.
On Tue, 24 Feb 2009 02:56:11 +0530 wrote
>
>
>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
>>
On Thu, Feb 26, 2009 at 12:38 PM, Carl Johnstone
wrote:
> 1) We want to run different versions of the same app for different sites -
> this means I have a namespace problem for MyApp v1 vs MyApp v2 etc.
This has been discussed many times on the list. You can't run two
modules with the same name
Get a fairly typical mod-perl setup.
We have two load-balanced servers acting as front-end. They run threaded
apache configured for lots of connections and KeepAlive on. They serve up as
much stuff statically as possible, everything else is sent through
mod_proxy_balancer to a number of backend
On Thu, Feb 26, 2009 at 4:01 PM, Matthew Lenz wrote:
> Maybe the debian guys did something goofy with the modules. It wouldn't
> be the first time. That or maybe its just a bug in ModPerl. Even if
> some CPAN module out there has 'use warnings;' in it that shouldn't have
> any affect on any cod
Maybe the debian guys did something goofy with the modules. It wouldn't
be the first time. That or maybe its just a bug in ModPerl. Even if
some CPAN module out there has 'use warnings;' in it that shouldn't have
any affect on any code outside of its own package should it?
I think that Moose
On Thu, 2009-02-26 at 15:49 -0500, Adam Prime wrote:
> André Warnier wrote:
> > Matthew Lenz wrote:
> >> I can't seem to disable warnings on our production environment. 'use
> >> warnings' is not included in any of the config/startup/scripts or custom
> >> modules. Its possible I guess that its b
André Warnier wrote:
Matthew Lenz wrote:
I can't seem to disable warnings on our production environment. 'use
warnings' is not included in any of the config/startup/scripts or custom
modules. Its possible I guess that its being used by a CPAN module.
We had a system on Debian 3.1 (apache/mod_
Matthew Lenz wrote:
I can't seem to disable warnings on our production environment. 'use
warnings' is not included in any of the config/startup/scripts or custom
modules. Its possible I guess that its being used by a CPAN module.
We had a system on Debian 3.1 (apache/mod_perl 1.x)and I have be
I can't seem to disable warnings on our production environment. 'use
warnings' is not included in any of the config/startup/scripts or custom
modules. Its possible I guess that its being used by a CPAN module.
We had a system on Debian 3.1 (apache/mod_perl 1.x)and I have been doing
work to migra
> > 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
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
> >
> > 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
12 matches
Mail list logo
