Front page | perl.qpsmtpd |
Postings from April 2012
logging
From:
Matt Simerson
Date:
April 7, 2012 21:27
Subject:
logging
Message ID:
03DFF5FD-7D9E-4DD6-9B69-488524F0A237@tnpi.net
It seems logging is an area of qpsmtpd that is ripe for improvement, but I'm not going to toss my hat into the ring against logterse, it looks like a great solution I may adopt later. For now, I'd like to make the built-in logging a little less crusty. In attempting to figure out where it was that I needed to edit to set the logging level, I found at least 4 different places:
• Qpsmtpd::TraceLevel => LOGWARN
• config/logging =>
logging/warn 4
logging/adaptive [accept minlevel] [reject maxlevel] [prefix char]
• config/loglevel => 4
• config/plugins
logging/syslog loglevel LOGINFO priority LOG_NOTICE
I suspect the latter is an error in the plugins/logging/syslog POD, where it says:
> =head1 CONFIGURATION
>
> To enable the logging plugin, add a line of this form to the qpsmtpd plugins
> configuration file:
I think that it should say to place that configuration in the config/logging file. But since there's no user documentation, I had to read the other logging plugins to arrive at that conclusion.
There is docs/logging.pod, but that is strictly developer documentation. There's no document that explains to a qpsmtpd user (ie, not a developer) which of the places he needs to go and edit, and when, to get the desired effects. I'll document qpsmtpd logging, but I'd like to have a git of a historical perspective on it.
Why/when is is necessary to edit $Qpsmtpd::TraceLevel?
Why/when is it config/loglevel consulted?
When a plugin is chosen in config/logging, is it additive to qpsmtpd's default logging, or does it replace it?
Are the above settings how they are/were supposed to work? Is that how we want them to work in the future?
Matt
`````````````````````````````````````````````````````````````````````````
Matt Simerson http://matt.simerson.net/
Systems Engineer http://www.tnpi.net/
Mail::Toaster - http://mail-toaster.org/
NicTool - http://www.nictool.com/
`````````````````````````````````````````````````````````````````````````