freshclam logs in two different places depending on whether it's called from clamd or from the cron job. Cron job logs where the config file specifies, but when clamd calls freshclam on startup, it uses clam-update.log (which I don't find mentioned in any of the config files or in the startup script--is it hardcoded?)
No. But that's the name used in the manual, freshclam.log is the default in the configuration file... probably a previous installation used the instructions on the manual.
Didn't understand that freshclam was being run as a daemon by the startup script (my other systems don't have that) so I removed the cron script.
Was clamav installed using emerge?
Yes, 'emerge clamav' and everything seemd to go well.
The first thing to check is Rob's suggestion, you may have a second clamav
installation perhaps in /usr/local/{bin, sbin, etc}.
Checked that earlier, since the manual builds I did on other systems installed there (after binary installs used /usr/bin and /usr/sbin, necessitating some symlinks to keep everything happy.) On this system, both /usr/local/bin and /usr/local/sbin are completely empty.
_______________________________________________ http://lurker.clamav.net/list/clamav-users.html
