Re: [Qmail-scanner-general]CPU Hog

2004-04-05 Thread Nelson D. Guerrero
On [05/04/2004], Niek Baakman wrote: > > It probably is Nelson. > Just for stats sake, how many emails does your server handle per second, or > per minute ? It's well over the 150 mark. I suppose that most of it is virus and spam. > > Regards, > Niek Baakman > -- > > The greatest trick

Re: [Qmail-scanner-general]CPU Hog

2004-04-05 Thread Niek Baakman
Nelson D. Guerrero wrote: On [05/04/2004], Nelson D. Guerrero wrote: [snip] Well, I managed to fix the problem. It was a permission problem in /usr/local/share/clamav, it had clamav:clamav when it should have qscand:qmail :). Thanks to everyone who helped me in this time of need ;)

Re: [Qmail-scanner-general]CPU Hog

2004-04-05 Thread Nelson D. Guerrero
On [05/04/2004], Nelson D. Guerrero wrote: > > [snip] Well, I managed to fix the problem. It was a permission problem in /usr/local/share/clamav, it had clamav:clamav when it should have qscand:qmail :). Thanks to everyone who helped me in this time of need ;). load average: 1.00,

Re: [Qmail-scanner-general]CPU Hog

2004-04-05 Thread Nelson D. Guerrero
On [05/04/2004], Will Saxon wrote: > > Have you set up the clamav databases, etc.? > > I found that I had this happen all the time with the latest 'stable' version > of clamav on FreeBSD 5.2.1. However, when I used the clamav-devel port > (clamav 20040321 snapshot) I did not have the problem anym

Re: [Qmail-scanner-general]CPU Hog

2004-04-05 Thread Nelson D. Guerrero
On [05/04/2004], [EMAIL PROTECTED] wrote: > > in qmail-scanner-queue.pl, set the path to clamscan to use clamdscan. many > orders of magnitude faster than plain clamscan. you'll of course need to > set up the clamd daemon first. > > > Paul Theodoropoulos > http://www.anastrophe.com > Forgot t

RE: [Qmail-scanner-general]CPU Hog

2004-04-05 Thread Will Saxon
> I did this following your sugestions and got the following errors > while procesing messages: > > clamscan: corrupt or unknown ClamAV scanner error or > memory/resource/perms problem > - exit status 2 > > I did a google search on the error and found that a person fixed a > simil

Re: [Qmail-scanner-general]CPU Hog

2004-04-05 Thread Nelson D. Guerrero
On [05/04/2004], [EMAIL PROTECTED] wrote: > > in qmail-scanner-queue.pl, set the path to clamscan to use clamdscan. many > orders of magnitude faster than plain clamscan. you'll of course need to > set up the clamd daemon first. > > > Paul Theodoropoulos > http://www.anastrophe.com > > I

RE: [Qmail-scanner-general]CPU Hog

2004-04-05 Thread Will Saxon
> -Original Message- > From: Nelson D. Guerrero [mailto:[EMAIL PROTECTED] > Sent: Monday, April 05, 2004 3:04 PM > To: [EMAIL PROTECTED] > Subject: Re: [Qmail-scanner-general]CPU Hog > > > On [05/04/2004], Christian Lyra wrote: > > hi, > > >

Re: [Qmail-scanner-general]CPU Hog

2004-04-05 Thread Nelson D. Guerrero
On [05/04/2004], Christian Lyra wrote: > hi, > > are you runnind the clamav daemon? > I'm actually not running the daemon. I followed a web install and it didn't mention me running the daemon. I suppose that clamscan runs when qmail-scanner invokes it. -- nelsong; (gre

Re: [Qmail-scanner-general]CPU Hog

2004-04-05 Thread Christian Lyra
hi, are you runnind the clamav daemon? On Monday 05 April 2004 15:03, Nelson D. Guerrero wrote: > Hello List, > > I have a little machine running Qmail+Vpopmail+Qmail-Scanner+ClamAV for > little over 14,000 people. > > I started using qmail-scanner last Friday and am having problems with

Re: [Qmail-scanner-general]CPU Hog

2004-04-05 Thread qmail-scanner
At 11:03 AM 4/5/2004, Nelson D. Guerrero wrote: --scanner clamscan --notify none --add-dscr-hdrs no --archive 0 --lang es_ES --log-details syslog (I've switched this from syslog to "no" without good results) --admin virusadmin Can anybody give me information on what might be going on

[Qmail-scanner-general]CPU Hog

2004-04-05 Thread Nelson D. Guerrero
Hello List, I have a little machine running Qmail+Vpopmail+Qmail-Scanner+ClamAV for little over 14,000 people. I started using qmail-scanner last Friday and am having problems with CPU usage. The machine is a dual PIII 800MHz, 512MB ram, 1 120G WD hdd and 1 20G Seagate hdd, running Slackware 9.