On 09/22/2014 06:23 PM, David Cain wrote: > Hi all, > > I'm running ClamAV work amavisd-new on a Debian Wheezy server. I > update the serve with security and s/w updates weekly, so it's on the > latest now for the distro. > > Every Sunday at exactly 9PM EDT (0100 UTC), cron sends me an email > that freshclam.log is locked. Thing is, I'm not running freshclam > with cron, and there's not ANYTHING in crontab, cron.d, cron.hourly, > cron.daily or cron.weekly that's supposed to be running at that > time. > > Any idea what's going on? Any thoughts appreciated.
It's not exactly an elegant solution, but you could use cron to schedule an `lsof /var/log/clamav/freshclam.log` at exactly 0100 UTC and figure out what has it locked. A `ps aux` or whatever at the same time would also help. _______________________________________________ Help us build a comprehensive ClamAV guide: https://github.com/vrtadmin/clamav-faq http://www.clamav.net/contact.html#ml
