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 things a couple of times per day. I'd rather wait the extra few (10?) seconds.
This makes room for my many Firefox windows, each with many tabs, which altogether eat much more RAM (about 6.5 GB resident, 46 GB virtual). But I use them far more often, and need their rapid response. On Sat, 09 May 2020 21:15:35 +0300 iulian stan via clamav-users <clamav-users@lists.clamav.net> wrote: > 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 > need to wait to load the virus database on each run. > > --- > Best regards, > Iulian > > On 2020-05-09 18:43, Christian wrote: > > > 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 service clamd: > > > > _sudo apt-get install clamav-daemon_ > > > > Scanning is much faster now. > > > > My question is: Is it alright to have clamav and clamav-daemon installed > > alongside each other? > > So that I can run either "clamscan somefile" or "clamdscan somefile"? > > > > Thanks a lot in advance. > > > > Greetings. > > Rosika _______________________________________________ clamav-users mailing list clamav-users@lists.clamav.net https://lists.clamav.net/mailman/listinfo/clamav-users Help us build a comprehensive ClamAV guide: https://github.com/vrtadmin/clamav-faq http://www.clamav.net/contact.html#ml
