Crist J. Clark <[EMAIL PROTECTED]> a écrit :
> It sounds like you have spamd writing _directly_ to the log file
> rather than actually using the syslog service?
I don't think so. Spamd is using the syslog-ng service with the mail
facility (the default). Spamd stops logging when syslog-ng is stop
On Sun, Jul 07, 2002 at 05:15:12PM +0200, Nicolas STRANSKY wrote:
> Michael Breuer <[EMAIL PROTECTED]> a écrit :
>
> > Aha... you need to modify your logrotate scripts to restart spamd. On
> > linux, there is a /etc/logrotate.d directory which contains rulesets
> > for each service & how to rest
Michael Breuer <[EMAIL PROTECTED]> a écrit :
> Aha... you need to modify your logrotate scripts to restart spamd. On
> linux, there is a /etc/logrotate.d directory which contains rulesets
> for each service & how to restart (kill -HUP, etc.)
Ok, in fact that's what I have done : I've noticed th
Aha... you need to modify your logrotate scripts to restart spamd. On
linux, there is a /etc/logrotate.d directory which contains rulesets for
each service & how to restart (kill -HUP, etc.)
Nicolas STRANSKY wrote:
>hello,
>
>In fact, i've installed spamassassin 2.31 to see if it could solve
hello,
In fact, i've installed spamassassin 2.31 to see if it could solve the
problem and here is what i've noticed : spamassassin stops to log every day
just after the logrotate has finished rotating the logs and that syslog-ng
has been restarted. If I restart spamd, then it logs connections aga
