micah wrote: > On Wed, 19 Sep 2007 18:37:13 +0000, micah wrote: > >> The logrotate.d/clamav does this: >> >> 1. Moves clamav.log to clamav.log.1 >> 2. runs: /etc/init.d/clamav-daemon reload-log, which is effectively a >> kill -1 (ie. HUP). >> >> I've got the following associated config lines in clamd.conf: >> >> LogSyslog false >> LogFacility LOG_LOCAL6 >> LogClean false >> LogVerbose false >> LogFile /var/log/clamav/clamav.log >> LogTime true >> LogFileUnlock false >> LogFileMaxSize 0 > > It seems like if I set LogSyslog true and then send a -HUP to clamd it > reloads the syslog logging, but not the LogFile based logging. I guess I > will switch to Syslog based logging, but this seems like a bug. >
If you yank the log file out from under syslogd then you need to discover how your syslogd will react. In my Solaris environment I kill -HUP the syslogd after rotating logs. Solaris has a couple different ways to rotate logs built in to the OS so I have simply added the clam logs to that process and use syslogd as clamav's logger. dp _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://lurker.clamav.net/list/clamav-users.html
