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
#
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.
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
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
I've been looking for a way to get l4p to tell me where the config under
which it's running comes from. Essentially, I'd like to have a method
that would return the full path to the config file that it's currently
using.
Obviously, there are complications, such as those relating to
programatic c
On Thu, 28 Jun 2007, Berg, Eric wrote:
> I've been looking for a way to get l4p to tell me where the config
> under which it's running comes from. Essentially, I'd like to have
> a method that would return the full path to the config file that it's
> currently using.
>
> Obviously, there are comp
On Thu, 28 Jun 2007, Berg, Eric wrote:
> Are there any best practices, examples, etc. for the best way to
> provide a wrapper to log?
Here's a couple of hints:
http://log4perl.sourceforge.net/d/Log/Log4perl.html#6acb7
> I'm using some of the sample code that provides a _get_logger()
> funct
I do store it in my app, but I've set up my wrapper to look for an
environment variable first, then a local whatever.ini, and then a full
path to the default. I am trying to work with my other developers to
initialize "properly", but sometimes they don't and when that happens,
it often leads to a
