> > I think plugins are a little too heavy for this.
>
> Why? We have config plugins - are they too heavy?
config and logging is orthogonal. If logging breaks, you don't find
out that other things broke. We also tend to do a lot of logging.
At a first approximation:
[EMAIL PROTECTED] ~/projects/qpsmtpd$ grep -r -- '->config' * | wc -l
65
[EMAIL PROTECTED] ~/projects/qpsmtpd$ grep -r -- '->log' * | wc -l
206
plugins are, by their nature, fragile. I'm just not sure I like my
logging to be fragile.
Our current plugin system also calls load_plugins too often. (Ok,
it's just that rogue call in TcpServer::run that should probably be
removed.)
> > Log::Dispatch is tailor made for this. (Which I'd prefer to see used
> > instead of hacking syslog support in.)
>
> Yeah, but L::D has a boat load of dependencies (IIRC). Right now
> running qpsmtpd is as easy as untarring the distro and doing ./run -
> I'd rather not break that if we can help it.
We've already got external dependencies on some of the MIME
libraries.
Log::Dispatch has no dependencies except what's needed for the
particular mechanism you're using. I.e.
Sys::Syslog for syslog.
I just don't see this particular wheel as one that needs to be
reinvented. (Especially as Log::Dispatch and it's associated
subclasses (available separately) gets us every kind of logging we
could ever want.
(Including Jabber, Database, 3 different kinds of rotated output
files, Windows, Apache, etc.. and yes - those are the esoteric ones.)
-R
