On Tue, 16 Nov 2004 at 20:15:21 -0600, C. Bensend wrote:
[...]
I am running clamd and freshclam successfully. I'd like to use
clamdscan to speed things up, but it doesn't appear to support the --move
option that clamscan does. It points me to clamd.conf, which doesn't
mention anything
Tomasz Papszun wrote:
I am running clamd and freshclam successfully. I'd like to use
clamdscan to speed things up, but it doesn't appear to support the
--move option that clamscan does. It points me to clamd.conf, which
doesn't mention anything about a config file option for --move
C. Bensend wrote:
Or as a workaround, clamd can be wrapped in a shell script which will
move the infected files to a quarantine directory.
I'm assuming you meant 'clamdscan' above?
Yes. My brain and fingers work at vastly varying degrees of cooperation
on occasion :)
Matt
On Wed, 17 Nov 2004 at 8:06:22 -0600, C. Bensend wrote:
Until it is added, you'll have to use clamscan. Note though, that if you
scan many files at once (with one launching of clamscan), performance
increasing thanks to using clamdscan instead of clamscan - is
negligible (because the
Last night, in an attempt to stop the Virus Found notifications being
sent to a false sender address by the Worm.SCO.A, I added to my
silent_viruses_array in the Q-S.pl script 'worm.sco.a'. (right after
'klez','bugbear')
As soon as I did that, clamav stopped recognizing the virus.
I had been
