Re: [Clamav-users] Lame mirror at [67.15.61.160]

2008-09-29 Thread Paul Griffith
(434940 signatures) from db.ca.clamav.net (IP: 24.215.0.24) Sat Sep 27 20:28:32 2008 - Clamd successfully notified about the update. Sat Sep 27 21:28:01 2008 - -- -- Paul Griffith ___ Help us build a comprehensive

[Clamav-users] Handling mail surges

2007-09-12 Thread Paul Griffith
Greetings, Does any one have any suggestions for handling spam surges? We had a spam mail surge and exim was getting connection timeout errors from the clamd socket, for spamassassin we can increase the number of child processes to handle more connections. Any best of practices out there ?

Re: [Clamav-users] Handling mail surges

2007-09-12 Thread Paul Griffith
On Wed, 12 Sep 2007 10:57:33 -0400, Paul Griffith [EMAIL PROTECTED] wrote: Greetings, Does any one have any suggestions for handling spam surges? We had a spam mail surge and exim was getting connection timeout errors from the clamd socket, for spamassassin we can increase the number

Re: [Clamav-users] error can't create lock file database directory

2007-06-05 Thread Paul Griffith
On Sat, 02 Jun 2007 03:38:55 -0400, night duke [EMAIL PROTECTED] wrote: how can i fix this? does anyone know when will be released the rpm files of version 0.90.3? Thanks freshclam --debug ClamAV update process started at Sat Jun 2 03:24:50 2007 LibClamAV debug: Can't create Lock

[Clamav-users] freshclam - ERROR: Can't lock database directory: - stale .dbLock file

2007-02-22 Thread Paul Griffith
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

Re: [Clamav-users] freshclam - ERROR: Can't lock database directory: - stale .dbLock file

2007-02-22 Thread Paul Griffith
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: /cs/local