-
From: Rob MacGregor [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 12, 2005 5:12 PM
To: ClamAV users ML
Subject: Re: [Clamav-users] freshclam 0.80 on FreeBSD hanging
On Wed, 12 Jan 2005 13:50:01 -0500, Jason Hammerschmidt
[EMAIL PROTECTED] wrote:
freshclam (0.80) as compiled from
Hi,
Date: Wed, 12 Jan 2005 22:11:50 +
From: Rob MacGregor [EMAIL PROTECTED]
Message-Id: [EMAIL PROTECTED]
(snip)
On Wed, 12 Jan 2005 13:50:01 -0500, Jason Hammerschmidt
[EMAIL PROTECTED] wrote:
freshclam (0.80) as compiled from ports on a FreeBSD 4.10 box
What's in your freshclam.conf?
In my case, above was the key.
Check your /usr/local/etc/freshclam.conf compared to
/usr/ports/security/clamav/work/clamav-0.80/etc/freshclam.conf .
It was caused by following changes in freshclam.conf were not
reflected on existing
On Thu, 13 Jan 2005 at 10:44:19 -0500, Jason Hammerschmidt wrote:
DatabaseDirectory /var/db/clamav
PidFile /var/run/clamav/freshclam.pid
I have those two lines, here is the contents of my entire freshclam.conf
file without comments
wmail1# grep -v ^# freshclam.conf | sort | uniq
freshclam (0.80) as compiled from ports on a FreeBSD 4.10 box seems to run
on it's own for a period of time, then although the process is still alive,
just seems to stop doing any work. Witness the below, set to check 48 times
a day, or once every 30 minutes, performs one check, then does
Jason Hammerschmidt wrote:
tailing the log files while also running the command in verbose mode. Any
ideas why it hangs? Is it checking but not logging or telling me?
wmail1# freshclam -v -c 48
It's doing exactly whet you told it to do, just not what you *want* it
to :-).
To have it stay
It's doing exactly whet you told it to do, just not what you
*want* it to :-).
To have it stay active and check every 30 minutes, add the
'-d'/'--deamon' option.
But with that option, according to the logs, it looks as if freshclam just
stops checking and updating.
Jason Hammerschmidt wrote:
To have it stay active and check every 30 minutes, add the
'-d'/'--deamon' option.
But with that option, according to the logs, it looks as if freshclam just
stops checking and updating.
If it truly does check a few times and then stops doing it, that's
weird. Do you
On Wed, 12 Jan 2005 13:50:01 -0500, Jason Hammerschmidt
[EMAIL PROTECTED] wrote:
freshclam (0.80) as compiled from ports on a FreeBSD 4.10 box seems to run
on it's own for a period of time, then although the process is still alive,
Checking my own server's freshclam log (clamav-0.80_2) it works
