Paul Griffith wrote:
> Has anyone encountered the following problem:
>
> Somehow there was a stale .dbLock file in the database directory, and
the
> log file was full of
> 'ERROR: Can't lock database directory: /cs/local/share/clamav' I did a
strace and saw the freashclam was trying to create a
> I haven't seen a stale .dbLock file, but both freshclam and clamd 0.90
have been dying with "Can't lock database > directory" every
time a new version of signatures comes out. This is on a RedHat
Advanced Server 4 system. I have > pasted portions of the logs
below. Freshclam runs
Brian wrote:
> both freshclam and clamd 0.90 have been dying with
> "Can't lock database directory" every time a new
> version of signatures comes out.
It looks like my problem was caused by having freshclam run
a script after an update using the OnUpdateExecute line in
freshclam.conf. The
