Better, I think, is to start with what processes can lock the log file.
Logrotate being one such. It is a small matter to disable this and wait and see.
dp
On 9/23/14 8:50 AM, Kevin Lin wrote:
Have you tried to query what process is locking the log file?
It is possible that multiple freshclam instances are running at the same
time, especially if an instance of freshclam is running as a daemon.
On Linux, you can use a command such as "lsof | grep freshclam.log" to
identify what process is locking a freshclam.log.
-Kevin
On Mon, Sep 22, 2014 at 6:26 PM, David Cain <sblkclamav-us...@jimmiedave.com
wrote:
ERROR: Problem with internal logger (UpdateLogFile =
/var/log/clamav/freshclam.log).
ERROR: /var/log/clamav/freshclam.log is locked by another process
DC
_______________________________________________
Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq
http://www.clamav.net/contact.html#ml
_______________________________________________
Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq
http://www.clamav.net/contact.html#ml
_______________________________________________
Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq
http://www.clamav.net/contact.html#ml
