John Fleming wrote:
- And the clamav log is free of errors and indicated that the
database is updated appropriately and clamd is being notified of
changes.
OK, clamav is finding viruses again, but they are not being LOGGED in
/var/log/clamav.log. The database upgrades and any restarts ARE being
logged - just not the "FOUND <virusname>" that I'm used to. (Thus my
virus stats programs are no good.) The header of the infected emails
does have the FOUND <virusname> - just not the log. I've googled this
and found one suggetion to no avail. clamd.conf indicates the proper
path to the log and, again, some activity gets logged. Debian stable,
clamav 0.90.1 Calling with clamassassin 1.2.4 (latest update to work
with 0.90) Any more ideas or troubleshooting? Thanks - John
Are you using syslog to log clam entries or letting clamd do the
logging? If not syslog, then the the clamd run-as user have write
permissions to the log? Is the log < 2gig in size? If syslog is used, is
the facility in the syslog.conf file for the clamav.log file the same as
that in the clamd.conf file?
dp
_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://lurker.clamav.net/list/clamav-users.html
