Re: [log4perl-devel] When a missing config file

[John O. <joh...@o-...>]

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 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
>
>  
>
>  
>
> #                       The Postfix program
>
> #
>
> # <tq...@uk...>: Command died with status 2: "perl
>
> #     -I/home/lgoddard/trafficjam/trunk/lib 
> -MTrafficJam::Controller::Root -e
>
> #     'warn TrafficJam::Controller::Root->mail_in'". Command output: 
> Cannot open
>
> #     config file '/home/lgoddard/trafficjam/trunk/config/mail.l4p' at
>
> #     /usr/local/share/perl/5.8.4/Log/Log4perl/Config.pm line 619, 
> <STDIN> line
>
> #     26.
>
> #
>
>  
>
> Lee Goddard
>
> Senior Software Developer
>
> Advertising.com, London
>
>  
>
> P Think of the environment before you print this email
>
>  
>
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> ------------------------------------------------------------------------
>
> _______________________________________________
> log4perl-devel mailing list
> log...@li...
> https://lists.sourceforge.net/lists/listinfo/log4perl-devel
>