If this helps:
I am using Log4Perl in a typical forked-to-background-daemon.
I had to do a little thinking to figure out the best place to initialize
Log4Perl.
The problem is, that the utilized shared vars lost their sharedness in the
child proc.
Maybe you have to initialize your Log4Perl-Obje
On Wed, Oct 15, 2008 at 9:47 PM, Chas. Owens <[EMAIL PROTECTED]> wrote:
> On Wed, Oct 15, 2008 at 06:04, Rob Coops <[EMAIL PROTECTED]> wrote:
> > Hi all,
> >
> > I am a little stumped here, I have a nice little application that makes
> use
> > of Log4perl (which I really like a lot) and now that
On Wed, Oct 15, 2008 at 06:04, Rob Coops <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> I am a little stumped here, I have a nice little application that makes use
> of Log4perl (which I really like a lot) and now that all the basic
> functionality is in there I have started working on makking things go
