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 currently implemented, a logger is only
On Thu, 18 Nov 2010, 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 currently implemented, a logger is only meaning
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
On Tue, 16 Nov 2010, Tom Metro wrote:
> 1. Ability to create a library module that can use Log4perl, such that
> if the calling code makes no use of Log4perl, it logs independently
> with locally specified defaults, but if the caller does use Log4perl,
> it picks up the callers settings.
Hi Tom,
