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, Ma
case the config has chanced, there is an init-and-watch
> method.
>
> If it is to combine configurations, the Hash::Merge module can help, and
> there is a working example somewhere in the archives of this group.
>
> HTH
>
>
> On 15/03/2013 21:54, Marc Zampetti wrote:
>
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
