;
#
Thanks
Richard
-Original Message-
From: Mike Schilli [mailto:m...@perlmeister.com]
Sent: 20 May 2009 22:25
To: Richard Burton
Cc: log4perl-devel@lists.sourceforge.net
Subject: Re: [log4perl-devel] Log4perl and catching unhandle
exceptions but not using 'easy' mode
On Wed, 20 May
On Wed, 20 May 2009, Robert Jacobson wrote:
Here's what I did: 1. Make a file trapper.pl. It's basically the
same as the example, except the Log4perl init, which uses a config
file (in this case, with a SIGHUP to re-read it):
Looks ok at first glance, doesn't it produce the expected output?
and catching unhandle
exceptions but not using 'easy' mode
On Wed, 20 May 2009, Richard Burton wrote:
I can catch this using stealth as loggers outlined in
http://search.cpan.org/~mschilli/Log-Log4perl/lib/Log/Log4perl
/FAQ.pm#So
me_module_prints_messages_to_STDERR
...@perlmeister.com
Does that help?
Richard
-Original Message-
From: Mike Schilli [mailto:m...@perlmeister.com]
Sent: 20 May 2009 22:25
To: Richard Burton
Cc: log4perl-devel@lists.sourceforge.net
Subject: Re: [log4perl-devel] Log4perl and catching unhandle
exceptions but not using
On Wed, 20 May 2009, Richard Burton wrote:
I can catch this using stealth as loggers outlined in
http://search.cpan.org/~mschilli/Log-Log4perl/lib/Log/Log4perl/FAQ.pm#So
me_module_prints_messages_to_STDERR._How_can_I_funnel_them_to_Log::Log4p
erl?
but the example assumes you are using the
Richard Burton richard-at-atomwide.com |log4perl_sourceforge| wrote:
Hi all
I am trying to capture unhandled exceptions that are sent to STDERR,
e.g. for example the following could would give such an error
[snip]
I can catch this using stealth as loggers outlined in
