that was the idea, but now i see that's not going to work. originally i
just wanted to change the log level on the root logger, which actually did
persist (i was dumb and spaced the fact that i was bypassing the embedded
perl engine when i was testing), but that only affected the one
interpreter
On Wed, 18 Apr 2012, Martin J. Evans wrote:
> panic: sv_setpvn called with negative strlen at
> /home/perlbrew//perls/perl-5.14.2/lib/site_perl/5.14.2/Log/Log4perl/Layout/PatternLayout.pm
> line 358.
This looks like a bug in perl, not Log4perl. Since Log4perl is pure
Perl, there should never be
On Wed, 18 Apr 2012, Gangemi, Jae wrote:
> actually, no - the call into the system could be considered the
> equivalent of running a cgi script inside of mod_perl, there is no signal
> handler involved, but i now realize my original approach just isn't going
> to work.
I see, and the reset to th
panic: sv_setpvn called with negative strlen at
/home/perlbrew//perls/perl-5.14.2/lib/site_perl/5.14.2/Log/Log4perl/Layout/PatternLayout.pm
line 358.
That line in my distribution is:
##
sub shrink_category {
###
actually, no - the call into the system could be considered the
equivalent of running a cgi script inside of mod_perl, there is no signal
handler involved, but i now realize my original approach just isn't going
to work.
the reason i'm not using 'init_and_watch()' is b/c we embed the
configur
