Hi altogether,
I´ve got a question regarding *clamscan* vs *clamdscan*.
My system is Linux/BodhiLinux 5.1.0 in a VM.
As antivirus-software I installed *clamav*:
/sudo apt-get install clamav clamav-freshclam/
Scanning procedure is good although a bit slow. So in addition to that I
installed the
Hi there,
On Sat, 9 May 2020, Christian wrote:
... Is it alright to have *clamav* and *clamav-daemon*
installed alongside each other?
So that I can run either "clamscan somefile" or "clamdscan somefile"?
You should really have asked that question on a mailing list for your
Linux distribut
Dear Christian,
It's normal that scanning with clamdscan takes a shorter time than
clamscan because the virus databases is already loaded (since it's a
daemon) and ready for action. For testing purposes(debugging, etc) you
can use clamscan for all other purposes use clamdscan where you don't
nee
On our mailserver, we run clamdscan, since mail arrives frequently (!).
On my workstation, I have switched to just using clamscan. Clamdscan
now uses so much resident memory (~ 1 GB), that even on my 32 GB
workstation I found it unreasonable to permanently tie up that much RAM
when I only scan thi
