Experienced it a few times after 0.90 was released (end february / first
half march)... Nothing changed in 0.90.1.
The nice thing is, freshclam still kept reporting that updates were
fine, after clamd went dead... Luckily, clam was configured as secondary
scanner in amavis, so mail delivery
Robert wrote:
It's only happened the once. By the time I inspected the
/usr/local/share/clamav
directory there was no sign of a .dbLock file.
However, the database directory is definitely writable by clamd.
It's owned by the clamav user.
Since the restart of clamd it has been behaving
clamd (ClamAV 0.90) died with following messages in the log:
Wed Feb 28 10:41:48 2007 - SelfCheck: Database status OK.
Wed Feb 28 10:52:12 2007 - SelfCheck: Database modification detected.
Forcing reload.
Wed Feb 28 10:52:12 2007 - Reading databases from /.../clamav
Wed Feb 28 10:54:22 2007 -
