> > On Mon, Feb 25, 2008, Birger Krägelin wrote: > > > On changing the default fsl configuration of spamassassin we found > > that spamassassin doesn't work with fsl. The default logfile was > > hardcoded in rc.spamassassin. After removing the startup option > > spamassassin logs to syslog. > > > > Platform is Solaris 10 Sparc. > > > > Any ideas? > > SpamAssassin is written in Perl and hence calls Perl's > vsyslog(3) function and hence OSSP fsl cannot intercept here. > But why do you want OSSP fsl here? Doesn't the > --syslog=/path/to/logfile (which is in > rc.spamassassin) work as expected? Or do you need OSSP fsl > for some non-file based logging?
This is one point, the other one is logfile rotating. The default way for openkpg packages is to rotate the logfiles and restart the servers every night. As we have heavy traffic and critical applications we cannot go offline. So wie modified fsl-descriptions to use "jitter" and "monitor" to allow for rotating without restart. But this does not work for all applications (e.g. spamassassin). I think about disabling fsl and moving to syslog-ng. Your thoughts? Birger ______________________________________________________________________ OpenPKG http://openpkg.org User Communication List openpkg-users@openpkg.org
