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 still some of Catalyst's -Debug s
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 still some of Catalyst's -Debug statements go
> to STDERR.
If those messages are
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 still some of Catalyst's -Debug statements go
to STDERR.
Is this a feature of Catalyst, or am I doing something wrong?
TIA
On Wed, 9 Jan 2013, Lee Goddard wrote:
> Is there a way to change the PatternLayout that the default Catalyst uses?
According to the Catalyst::Log::Log4perl code you can pass in your own
configuration file to specify a different layout and appender:
unless ( Log::Log4perl->initialized ) {
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
