Unless things have changed, razor supports both sys-syslog (log via
Perl's syslog) and also syslog (log via a direct socket to a syslog
server.) When the direct syslog was first implemented it did not
work at all - I tried it and it created a file called 'syslog'! I
patched the debian version enough that it at least worked on my machine.
On 1/11/2007, at 12:28 AM, Justin Mason wrote:
Francois Marier writes:
Hi Sven,
On 2007-10-31 at 10:28:26, Sven Hartge wrote:
I don't think that changing the logcheck rules is a proper fix. If
making razor log via syslog changes the way spamd represents itself,
there must be somethin fishy going on which should be
investigated and
not papered over.
You're right, it would be good to get to the bottom of this.
I would guess that it has to do with how SpamAssassin is calling
razor.
my guess is that Razor uses Sys::Syslog, the same module as
SpamAssassin
uses, and calls openlog() with a new "ident" string:
openlog $ident, $logopt, $facility
Opens the syslog. $ident is prepended to every message.
$logopt con-
tains zero or more of the words pid, ndelay, nowait. The
cons option
is ignored, since the failover mechanism will drop down to
the console
automatically if all other media fail. $facility specifies
the part
of the system to report about, for example LOG_USER or
LOG_LOCAL0: see
your syslog(3) documentation for the facilities available
in your sys-
tem. This function will croak if it can't connect to the
syslog dae-
mon.
this then replaces the SpamAssassin call to openlog().
it might be useful to open this bug upstream on the SA bugzilla,
we may be able to hack around it somehow.
--j.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
