http://bugzilla.spamassassin.org/show_bug.cgi?id=3052
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
------- Additional Comments From [EMAIL PROTECTED] 2004-04-28 16:21 -------
ok, I can't see how this can happen; all use of syslog() correctly specifies a
facility etc.
Anyway, I've fixed the code to always call openlog() first, since Sys::Syslog is
*very* clear that it's the only appropriate way to do it.
can you retry with current SVN (anything over rev 10385) and report if it fails
still? assuming it's fixed in the meantime.
aha, here's the conclusion: http://bugs.gentoo.org/show_bug.cgi?id=26694 states
that it's a bug in metalog.
------- Additional Comment #9 From Malte S. Stretz 2004-02-28 09:33 PST -------
This is no SpamAssassin bug but is caused by the Sys::Syslog module. As both
sysklog and syslog-ng work fine with this module, it is probably a bug in
metalog. In the metalog sources there's a part where the input is parsed and
which is marked as a kludge; I guess that's the culplrit but didn't have the
time to track it further down.
------- Additional Comment #10 From Michael Cummings 2004-02-29 04:08 PST
-------
I'm not sure this is a bug so much as a "feature" of Sys::Syslog. Sys::Syslog
was originally written to interface with Unix style syslog's - which are
generically similar to sysklog and syslog-ng, and nothing like metalog with its
"write intermittently features" (I don't use metalog, not a big fan, so that
last bit was unwarrantedly biased). SpamAssassin could use a different method of
writing to the system logs or could offer choices based on your syslog utility
of choice, but either way this really isn't a bug with gentoo. Gentoo's options
as I understand them are to either block users of metalog from using
SpamAssassin (NO, BAD), or to accept this and contact the SA folks to let them
know of the potential problem (which if I read the comments correctly has
already been done to some degree).
------- Additional Comment #11 From Malte S. Stretz 2004-02-29 05:19 PST -------
I am one of the "SA folks" :) I use metalog myself because it was once
recommended in the install guide and I looked for something more flexible than
sysklog; but I'll probably switch to syslog-ng soonish. We will probably just
mark this as a "known issue" in the README and good is.
As I said before, this is probably not a Sys::Syslog bug. It just writes to the
syslog socket in something which looks like some syslog formatted message.
metalog then obviously fails to identify this format, maybe thinking it already
has a date prepended or something.
Somebody might want to forward this to the metalog folks, but I don't think it
will help much as it seems like metalog is unmaintained and almost dead for at
least half a year now. (I am not even sure if I hadn't seen a bug report about
this in their tracker.)
Short conclusion: metalog is broken and dead. As long as some hardcore metalog
fan doesn't fix it, it will probably stay in this state forever.
given all that, I'll say if openlog() has fixed it, good; if not, then it's a
metalog bug and we're not going to be able to fix it from our end. ;)
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
You are on the CC list for the bug, or are watching someone who is.
