Re^2: Logging messages - is there a better way?

My vote goes to this module, as well. It makes it very easy to be flexible – you simply instrument your code with logging instructions, and then how much is logged and where is purely a matter of configuration. Very nice.

Makeshifts last the longest.

Comment on Re^2: Logging messages - is there a better way?

Replies are listed 'Best First'.
Re^3: Logging messages - is there a better way? by matt.tovey (Beadle) on Nov 18, 2005 at 14:49 UTC
Well, that was my first post on Perl Monks, and I was expecting to look back here tomorrow, and see if I had any replies. I certainly wasn't expecting 4 replies within half an hour! Thanks, people! I've seen log4j before, and would have gone for that, but it's not installed on the machines here. My script needs to be able to run on any of them, so editting syslog.conf is something I also want to avoid. However, Log::Dispatch is installed, and even though the Tklog option isn't, I think I should be able to code that in simply enough myself. :) Thanks for your help, Matt	[reply]

Replies are listed 'Best First'.

Re^3: Logging messages - is there a better way?
by matt.tovey (Beadle) on Nov 18, 2005 at 14:49 UTC

I've seen log4j before, and would have gone for that, but it's not installed on the machines here. My script needs to be able to run on any of them, so editting syslog.conf is something I also want to avoid.

However, Log::Dispatch is installed, and even though the Tklog option isn't, I think I should be able to code that in simply enough myself. :)

Thanks for your help,

Matt

[reply]