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

[Mike S. <m...@pe...>]

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.

Dumping a stack trace by default might be confusing to the casual L4p
user, but you can certainly use the following:

    use Log::Log4perl;
    use Carp;

    eval {
        Log::Log4perl->init(...);
    };

    if($@) {
        confess($@);
    }

Would this work for you?

-- Mike

Mike Schilli
m...@pe...



>
>
>
> 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
>
>
>
>