On Mon, 26 Feb 2007 23:41:39 -0800
Dennis Peterson [EMAIL PROTECTED] wrote:
Wolf, Brian wrote:
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
Tomasz Kojm wrote:
On Mon, 26 Feb 2007 23:41:39 -0800
Dennis Peterson [EMAIL PROTECTED] wrote:
Wolf, Brian wrote:
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
Dennis Peterson wrote:
Tomasz Kojm wrote:
On Mon, 26 Feb 2007 23:41:39 -0800
Dennis Peterson [EMAIL PROTECTED] wrote:
Wolf, Brian wrote:
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
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
Wolf, Brian wrote:
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
Greetings,
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 new .dbLock
Paul Griffith wrote:
Greetings,
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
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 new
On Thu, 22 Feb 2007 11:52:08 -0500, aCaB [EMAIL PROTECTED] wrote:
Paul Griffith wrote:
Greetings,
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:
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 as a
10 matches
Mail list logo
