Bookworm wrote:
That has its own flaws - namely, when it drops, it goes down hard for a
long time.
Daemonizing it using svcscan/tcpserver is the only real way to keep it
from going ga-ga on you.
Also, 18 megabytes isn't enough for the latest qmail-scanner with
ClamAV. I've found that 30 is now th
On Mon, Jun 14, 2004 at 10:10:59AM +1200, Jason Haar wrote:
> On Fri, Jun 11, 2004 at 09:59:06AM +, Payal Rathod wrote:
> > Nowhere is the time and date recorded. Can Jason or someone tell me is this a
> > known
> > bug in this version?
> >
> > Thanks a lot in advance and waiting eagerly for
On Fri, Jun 11, 2004 at 09:59:06AM +, Payal Rathod wrote:
> Nowhere is the time and date recorded. Can Jason or someone tell me is this a known
> bug in this version?
>
> Thanks a lot in advance and waiting eagerly for any answers.
>
Fixed in next release
--
Cheers
Jason Haar
Information
That has its own flaws - namely, when it drops, it goes down hard for a
long time.
Daemonizing it using svcscan/tcpserver is the only real way to keep it
from going ga-ga on you.
Also, 18 megabytes isn't enough for the latest qmail-scanner with
ClamAV. I've found that 30 is now the minimum.
Greg
Clamscan is not the client for clamd, clamdscan is.
This sounds like perm problem what user is q-s running as? What user is
calling clamdscan?
-Original Message-
From: Greg Kopp [mailto:[EMAIL PROTECTED]
Sent: Sunday, June 13, 2004 1:27 PM
To: Micha Silver
Cc: [EMAIL PROTECTED]; Jason Sta
I had the same problem.
I solved it by running clamd in daemon mode and running clamscan as a
client in qmail-scanner. Originally I was running clamdscan directly
from qmail-scanner (ala qmailrocks.org)
Greg
Micha Silver wrote:
Jason Staudenmayer wrote:
Bump up your softlimit and check the permi
What's in the clamd log? After you upgraded to your remove the clamd socket
file? The last time I updated that what it choked on. Just rm that file then
start the clamd and check the logs.
-Original Message-
From: Micha Silver [mailto:[EMAIL PROTECTED]
Sent: Sunday, June 13, 2004 4:27 AM
Jason Staudenmayer wrote:
Bump up your softlimit and check the permissions for the user running
clamdscan
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Friday, June 11, 2004 11:10 PM
To: [EMAIL PROTECTED]
Subject: [Qmail-scanner-general]clamdscan has problem?