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

2009-12-20 Thread Martin J. Evans
. Martin -- Martin J. Evans Easysoft Limited http://www.easysoft.com -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev

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

2010-01-06 Thread Martin J. Evans
if I see anything. I will also update the rt later today. Thanks again Martin -- Martin J. Evans Easysoft Limited http://www.easysoft.com On Wed, 9 Dec 2009, Martin Evans wrote: Mike Schilli wrote: On Wed, 9 Dec 2009, Martin Evans wrote: Since the upgrade we are getting no logging in one

[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

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

2011-11-17 Thread Martin J. Evans
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-linux-gnu-thread-multi Martin -- Martin J. Evans Easysoft Limited http://www.easysoft.com

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 other log4perl actions) if the log