[log4perl-devel] Can caller_depth be set per logger

2008-02-07 Thread Martin J. Evans
t the caller_depth to 2 but caller_depth seems to be global and hence this affects all other loggers in the same program. Is there any way to set caller_depth per logger? My precise example was in my post on this list 3-dec-07. Thanks Martin -- Martin J. Evans Easysoft Limited http://www.easysof

Re: [log4perl-devel] Change in behavior when upgrading to 1.26 and perl 5.10.0

2009-12-20 Thread Martin J. Evans
gt; 1.pl >> >> >> use Log::Log4perl qw(get_logger :levels); >> use DBIx::Log4perl; >> >> Log::Log4perl->init_and_watch('x.conf', 60); >> >> my $a = DBIx::Log4perl->new(); >> >> Log4perl.pm (put this in a dir ca

Re: [log4perl-devel] Change in behavior when upgrading to 1.26 and perl 5.10.0

2010-01-06 Thread Martin J. Evans
issue: > > https://rt.cpan.org/Ticket/Display.html?id=52913 > > Give it a spin! > > -- Mike > > Mike Schilli m...@perlmeister.com Thank you Mike. I've tried this now and it appears to fix the change in behaviour I reported and does not appear to break anything el

[log4perl-devel] Why is Log::Log4perl opening unreferenced log files and can I stop it

2010-07-07 Thread Martin J. Evans
to. This is rather annoying since it is using up my open file descriptors etc. Using lsof on a single daemon shows dozens of log files open even though there is NO chance it will log anything to them. Is there any way to stop this? Thanks. Martin -- Martin J. Evans Easysoft Limited http

Re: [log4perl-devel] Why is Log::Log4perl opening unreferenced log files and can I stop it

2010-07-08 Thread Martin J. Evans
n I change to Log::Log4perl::Appender::File and set the create_at_log it works fine. Martin -- Martin J. Evans Easysoft Limited http://www.easysoft.com > > > Martin J. Evans wrote: >> Hi, >> >> I have a number of daemon processes using Log::Log4perl and tens of >> mo

[log4perl-devel] logwarn not calling warn if L::L's init not called

2011-11-17 Thread Martin J. Evans
problem this morning only to discover this. I find this most worrying as I'd expect the warn to happen whatever. If you substitute logdie for die it seems to work. perl -MLog::Log4perl -le 'print $Log::Log4perl::VERSION;' 1.33 This is perl, v5.10.1 (*) built for i686-l

Re: [log4perl-devel] logwarn not calling warn if L::L's init not called

2011-11-21 Thread Martin J. Evans
On 21/11/11 04:46, Mike Schilli wrote: > On Tue, 1 Nov 2011, Martin J. Evans wrote: > >> So substituting warn with logwarn does not always warn! > > That's an interesting case. The way it's implemented right now is that > logwarn() will only call warn() (along with o

Re: [log4perl-devel] logwarn not calling warn if L::L's init not called

2012-01-03 Thread Martin J. Evans
On 24/12/11 01:01, Mike Schilli wrote: > On Mon, 21 Nov 2011, Martin J. Evans wrote: > >> Would you consider changing this? If not, I would be most grateful if >> you could you point me at the place where I could change this >> behaviour or tell my how I could override it

[log4perl-devel] panic in sv_setpvn

2012-04-18 Thread Martin J. Evans
y; } perl -MLog::Log4perl -le 'print $Log::Log4perl::VERSION;' 1.36 This is Perl 5.14.2 on Linux 32 bit machine built as default via perlbrew. Any ideas. Martin -- Martin J. Evans Easysoft Limited http://www.easysoft.com