Yes, /var/log/clam-update.log is owned by clamav.clamav and has 0644 permissions. Freshclam is run by root's cron script. It also make no difference whether I run it as a daemon (freshclam -d -c 2 -l /var/log/clam-update.log) or as a cron job (freshclam --quiet -l /var/log/clam-update.log). All my other logs are working fine. Can you suggest where else to look for the problem?
Thanks, Rick Knight ([EMAIL PROTECTED])
Odhiambo Washington wrote:
* Rick Knight <[EMAIL PROTECTED]> [20030211 01:12]: wrote:
Last Friday morning I started getting this error from my freshclam cron job ...
ERROR: LOGGER: Can't open file /var/log/clam-update to write. ERROR: Problem with internal logger.
Clamd and clamscan work fine and freshclam works without logging. I've checked file permissions and everything looks right. I would like to have the clamupdate logging working. Can anyone tell me how to fix this?
When you say "everything looks right", does this mean something like:
-rw-r--r-- 1 clamav clamav 17946 Feb 11 08:00 /var/log/clam-update.log
As in it's owned by user clamav???
-Wash
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
