On 28/03/2013 03:56, Mike Schilli wrote:
> On Wed, 27 Mar 2013, Lee Goddard wrote:
>
>> I'm trying Log::Log4perl::Catalyst in the way described in the SYNOPSIS
>> of the POD, with the configuration below. I get my own log statements in
>> the expected location but st
rong?
TIA
Lee
Config:
log4perl.logger = TRACE, FILE
log4perl.appender.FILE= Log::Log4perl::Appender::File
log4perl.appender.FILE.mode= append
log4perl.appender.FILE.filename =
/logs/engine/FifteenGifts-Engine/logs/l4p.log
log4perl.appender.FILE.layout=Log::Log4pe
I don't know the L4p source, but I vaguely recall that someone, years
ago, possibly in the Log4perl docs, said that the init method was only
intended to implement initialisation, not re-initialisation.
I may be wrong — I can't imagine ever calling init() twice, though I did
occasionally do it w
data to an appender of your
choice/via appenders listed in the config?
Lee
On 14/03/2013 17:25, Dmitry Bigunyak wrote:
> Hi there!
>
> I was searching the mailing-list history but didn't find any topics related
> to the subject I'd like to discuss. Maybe I didn't look c
Is there a way to change the PatternLayout that the default Catalyst uses?
It seems to default to logging to stderr, whilst tests default to out
putting to stdout, and the difference in the emptying of the buffers
makes the out-of-sync output hard to read.
TIA
Lee
From: Mike Schilli [mailto:[EMAIL PROTECTED]
> On Thu, 16 Aug 2007, Lee Goddard wrote:
>
> > Sometimes I need to just see the logging from a specific
> > method/subroutine/function.
> >
> > I realize I can change the log levels within that block of code, but
> &g
Thanks, Eric - that made sense, and the config is as I imagined.
I'm really into the ':easy' way, though, despite the OO nature of most of my
modules, so I'll have to start sub-classing, I think.
Thanks again
Lee
From: Berg,
d. Would it be a bad
idea to incorporate this?
Thanks
Lee
Lee Goddard
Senior Software Developer
Advertising.com, London
P Think of the environment before you print this email
-
This SF.net email is sponsored
ation file?
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: Splunk Inc.
Still grepping through log fil
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
initia
> -Original Message-
> From: John ORourke [mailto:[EMAIL PROTECTED]
>
> 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
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
Forgot to say thanks to all Log4perl developers for the multiline
Patternlayout. Thanks!
lee
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your
13 matches
Mail list logo
