Hi,
Clamscan
doesn’t rely on clamd, it’s just a standalone client.
To
access clamd you’ll have to connect by TCP or socket.
You
can lookup in your logs how many virus signatures you’ve available, or
just run a freshclam yourself, you’ll see it then as well.
Wouter
-Oorspro
Hi again,
Sorry for all the questions, but I'm still trying to get familiar with
how clamav works.
Is clamscan the client portion, which connects to clamd? Or is clamscan a
scanner by itself that doesn't rely on clamd?
Seems to me clamscan runs fine without clamd running. So I'm guessing
clamsc
Hi all,
How stable are the snapshots? Should I go with stable and steer away from
snapshots?
When is 0.55 due to be released?
Thanks
Ricardo
* Tomasz Kojm <[EMAIL PROTECTED]> [20030430 17:39]: wrote:
> > Hi!
> >
> > Just tested the latest snapshot of ClamAV, clamd seems completely dead.
> > Nothing happens when I run clamdscan. Is Clamd under FreeBSD just
> > working worse and worse?
>
>
* Daniel Wiberg <[EMAIL PROTECTED]> [20030430 15:43]: wrote:
> Hi!
>
> Just tested the latest snapshot of ClamAV, clamd seems completely dead.
> Nothing happens when I run clamdscan. Is Clamd under FreeBSD just
> working worse and worse?
True;-)
Go back to the previous
> Hi!
>
> Just tested the latest snapshot of ClamAV, clamd seems completely dead.
> Nothing happens when I run clamdscan. Is Clamd under FreeBSD just
> working worse and worse?
Please don't use clamav-20030424, it seems to be seriously broken.
Best regards,
Tomasz Kojm
--
oo.
Hi!
Just tested the latest snapshot of ClamAV, clamd seems completely dead.
Nothing happens when I run clamdscan. Is Clamd under FreeBSD just
working worse and worse?
--
Daniel Wiberg
www.wiberg.nu
-
To unsubscribe, e-mail: [
Hi,
I have tested clamd 20030424 with a 30 Meg .mbox file. In the file are
big .zip files with the test signature. Clamd find that testsignature,
but the problem is, that after each call to SCAN clamd uses more and
more memory and don't free's that. And with this big files..
I think, that
* Fajar Arief Nugraha <[EMAIL PROTECTED]> [20030430 13:51]: wrote:
> What? you downgraded? I upgraded because clamav-0.54 and clamav-20030403
> sometimes just dies, and I get
>
> 2003-04-29 00:10:06 19AC8F-0006zQ-00 temporarily rejected by exiscan():
> Temporary local probl
ROTECTED]> [20030430 11:22]: wrote:
I am getting enough errors from clamav this morning:
2003-04-30 11:11:51 19AmbZ-0004dr-C9 temporarily rejected by exiscan(): \
Temporary local problem (unable to read from ClamAV socket
Does this mean I have to increase some values in clamav.conf
My
* Wash <[EMAIL PROTECTED]> [20030430 11:22]: wrote:
> I am getting enough errors from clamav this morning:
>
> 2003-04-30 11:11:51 19AmbZ-0004dr-C9 temporarily rejected by exiscan(): \
> Temporary local problem (unable to read from ClamAV socket
>
> Does this mean I have
More info...
On average, I get this
ps ax | grep exim | awk '{print $1}' | wc -l
Exim+exiscan+clamav using TCP socket.
I have run this for months on end. I have also tried using local socket
but that seems to give more errors that the TCP socket.
I'd appreciate some tuning tips.
-Wash
--
I am getting enough errors from clamav this morning:
2003-04-30 11:11:51 19AmbZ-0004dr-C9 temporarily rejected by exiscan(): \
Temporary local problem (unable to read from ClamAV socket
Does this mean I have to increase some values in clamav.conf
My Exim server here is having as many as 200 child
Hi,
I'm using exim-exiscan-clamav combination on a Solaris 8 box running as
MTA that handles about 10 mail daily.
Sometimes clamd just stops for unknown reason. The process is simply
gone, and then exiscan would complain "could not connect to clamd socket".
Yesterday I updated clamav from cl
14 matches
Mail list logo
