-Original Message-
From: Mike Schilli [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 28, 2007 8:45 PM
To: Berg, Eric
Cc: Mike Schilli; [email protected]
Subject: RE: [log4perl-devel] When a missing config file
>> Another solution would be wildcard/regex cate
you very much.
-Eric
-Original Message-
From: Mike Schilli [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 28, 2007 8:45 PM
To: Berg, Eric
Cc: Mike Schilli; [email protected]
Subject: RE: [log4perl-devel] When a missing config file
On Thu, 28 Jun 2007, Berg, Eric wrote:
>
Mike Schilli [mailto:[EMAIL PROTECTED] wrote:
>
> On Thu, 28 Jun 2007, Lee Goddard wrote:
>
> > Please could Log/Log4perl/Config.pm line 619 offer a stack backtrace
as
> > well as barfing?
> >
> > My current project has four config files, several potential
initialisers
> > (bad idea, I know) and
Thanks!
-Eric.
-Original Message-
From: Mike Schilli [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 28, 2007 7:54 PM
To: Berg, Eric
Cc: [email protected]
Subject: Re: [log4perl-devel] When a missing config file
On Thu, 28 Jun 2007, Berg, Eric wrote:
> I've bee
>
> -Eric.
>
> -Original Message-
> From: Mike Schilli [mailto:[EMAIL PROTECTED]
> Sent: Thursday, June 28, 2007 7:54 PM
> To: Berg, Eric
> Cc: [email protected]
> Subject: Re: [log4perl-devel] When a missing config file
>
> On Thu
> -Eric.
>
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of John
> ORourke
> Sent: Thursday, June 28, 2007 6:42 AM
> To: Lee Goddard
> Cc: [email protected]
> Subject: Re: [log4perl-devel] When a missing config
D] On Behalf Of John
ORourke
Sent: Thursday, June 28, 2007 6:42 AM
To: Lee Goddard
Cc: [email protected]
Subject: Re: [log4perl-devel] When a missing config file
Try putting:
use Error;
in one of your modules/scripts - it will override the warn/die handlers
globally, so unles
Try putting:
use Error;
in one of your modules/scripts - it will override the warn/die handlers
globally, so unless Log4perl overrides them again it will give you a
stack trace.
cheers
John
Lee Goddard wrote:
>
> Please could Log/Log4perl/Config.pm line 619 offer a stack backtrace
> as w
Thanks for the tip, John: I don't recall the module, but it looks like a
good quick-fix, quicker than tracking-down and editing every version of
L4p I install !
But I'd still like the shortmess near configuration file errors, because
they're pretty common end-user errors.
> -Original Mess
On Thu, 28 Jun 2007, Lee Goddard wrote:
> Please could Log/Log4perl/Config.pm line 619 offer a stack backtrace as
> well as barfing?
>
> My current project has four config files, several potential initialisers
> (bad idea, I know) and reports only via e-mail, since it is part of a
> MTA process.
Please could Log/Log4perl/Config.pm line 619 offer a stack backtrace as
well as barfing?
My current project has four config files, several potential initialisers
(bad idea, I know) and reports only via e-mail, since it is part of a
MTA process.
Thanks in anticipation
Lee
#
11 matches
Mail list logo
