Mike Schilli wrote:
> Tom Metro wrote:
>> It came about because the $logger object doesn't actually convey the
>> full state, so when serialized and passed to a remote method, the
>> remote logging reverts to default logging settings.
>
> Yeah, the way it's cu
Mike Schilli wrote:
>> The trigger for the problem turned out to be a 'use' call in the eval'ed
>> code that loaded a library which internally called easy_init() (yet
>> specifying the INFO logging level).
>
> That's very confusing and should be avoided at all cost.
> We discourage people from doi
I like the API Log::Log4perl provides, but using Log::Log4perl v1.28
I've encountered issues with the internal implementation that have been
very time consuming to resolve.
Most relate to the way Log4perl seems to store state in global or class
variables rather than in object or instance variables
