-Original Message-
From: Aristotle Pagaltzis [mailto:pagalt...@gmx.de]
Sent: 13. novembra 2014 20:22
To: catalyst@lists.scsys.co.uk
Subject: Re: [Catalyst] Log4Perl and Catalyst startup routing table
Hi Adam,
* Adam Witney awit...@sgul.ac.uk [2014-11-13 12:45]:
I saw
On Thu Nov 13 2014 at 20:22:51 Aristotle Pagaltzis pagalt...@gmx.de wrote:
Hi Adam,
* Adam Witney awit...@sgul.ac.uk [2014-11-13 12:45]:
I saw this post, but I 'm not sure I can use it to get the Catalyst
normal startup output in my logs. Is this possible?
The problem with redirecting
* Adam Witney awit...@sgul.ac.uk [2014-11-12 13:55]:
I have Log4Perl controlling the logging in my Catalyst app, but I
can't seem to get the debug information from the normal Catalyst
startup (routing table, Loaded plugins etc) included into the Log4Perl
output.
Is it possible to log
Hi Adam,
* Adam Witney awit...@sgul.ac.uk [2014-11-13 12:45]:
I saw this post, but I 'm not sure I can use it to get the Catalyst
normal startup output in my logs. Is this possible?
I guess you could make half a work-around with this module, by writing
a plugin that uses the module to log this
Hi,
I have Log4Perl controlling the logging in my Catalyst app, but I can't seem to
get the debug information from the normal Catalyst startup (routing table,
Loaded plugins etc) included into the Log4Perl output.
Is it possible to log this output through Log4Perl?
Thanks
Adam
