No, adding Log::Log4perl->reset()
before the second call to Log::log4perl->init() doesn't fix anything. So
far, the only solution is to remove one of the calls to
Log::Log4perl->init().
Marc
On Sun, Mar 17, 2013 at 8:32 PM, Mike Schilli wrote:
> On Sat, 16 Mar 2013, Marc Zampetti wrote:
>
> So
On Mon, 18 Mar 2013, Marc Zampetti wrote:
No, adding Log::Log4perl->reset()
before the second call to Log::log4perl->init() doesn't fix anything. So
far, the only solution is to remove one of the calls to
Log::Log4perl->init().
Do you have some code that reproduces the problem so I can take a
On Sat, 16 Mar 2013, Marc Zampetti wrote:
So basically the question I have is that I need to reset and
re-configure the logging system at some point after the initial
logging setup. The docs for the init() and init_once() methods suggest
that calling init() a second time will "reset" and "overwr
The use case is the situation where I don't know what the config file with
the logging configuration is yet. So basically, the program does the
following:
1. Initializes the logging system as soon as it starts, before anything
else, with a basic config that will log to stdout.
2. Process the comma
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
I have a program that configures a basic Log4perl config so that I have
some sane logging until I'm able to read in the config file with the
final configuration. I'm getting an error when calling
Log::Log4perl->init() the second time that I cannot seem to track down.
From the reading of the do
