Quoting Neil Aggarwal <[EMAIL PROTECTED]>:
Hello:
On my server running Fedora Core2, I installed Clam AV version 0.72 from the dag rpms.
Here is what I did:
cd /usr/local wget http://dag.wieers.com/packages/clamav/clamav-0.72-1.1.fc2.dag.i386.rpm wget http://dag.wieers.com/packages/clamav/clamav-db-0.72-1.1.fc2.dag.i386.rp m wget http://dag.wieers.com/packages/clamav/clamd-0.72-1.1.fc2.dag.i386.rpm wget http://dag.wieers.com/packages/clamav/clamav-milter-0.72-1.1.fc2.dag.i38 6.rpm rpm -ivh clamav-0.72-1.1.fc2.dag.i386.rpm clamav-db-0.72-1.1.fc2.dag.i386.rpm clamd-0.72-1.1.fc2.dag.i386.rpm clamav-milter-0.72-1.1.fc2.dag.i386.rpm
Using crontab -e, I added this line to the crontab: 0 * * * * touch /var/log/clam-update.log ; chmod 0600 /var/log/clam-update.log ; chown clamav.clamav /var/log/clam-update.log ; /usr/local/bin/freshclam --quiet -l /var/log/clamav/clam-update.log
But, when freshclam runs, it gives me this error: ERROR: Can't open /var/log/clamav/clam-update.log in append mode. ERROR: Problem with internal logger.
The /var/log/clamav/clam-update.log is present and owned by clamav: ls -la /var/log/clam-update.log gives me: -rw------- 1 clamav clamav 0 Jun 14 14:29 /var/log/clam-update.log
If you read the error messages carefully you will see that in crontab you have
/var/log/clam-update.log
and the error from freshclam is:
/var/log/clamav/clam-update.log
Either you made a typo or you got multiple logs going on here. Either change the crontab or change /etc/freshclam.conf and point them to the same log file.
Jim
Jim
------------------------------------------------------- This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND _______________________________________________ Clamav-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/clamav-users
