>>> >>> Hello, >>> >>> But do I really need clamd?? >>> As far as I can tell, clamd "only" gives me on-access >>> protection, right? >>> >>> Thank you >>> Agostinho >>> >> >> No, clamd does not give to transparent backgroup >> protection, like the Windows antivirus tools to. It is a >> daemonized version of clamscan, which means that it >> preloads the signature databases to memory, and scans >> the viruses in rapid manner when requested, as it does >> not need to reload the database again and again >> everyting like clamscan has to. >> >> Its purpose is speed up the scanning process. If you are >> familiar with SpamAssassin, clamd works like spamd in >> SpamAssassin. >> >> clamd sits resident in memory, and the client, clamdscan >> works as its client, passing the material to clamd to >> process. This is fast and efficient compared to plain >> clamscan. Saves resources and time needed to scan. >> >> >> >> _______________________________________________ >> Help us build a comprehensive ClamAV guide: visit >> http://wiki.clamav.net >> http://www.clamav.net/support/ml > > > > Hello Jari, > > I see... so it's mainly a performance/efficiency thing. > Right? > > I thought it would provide me on-access scanning :-) > But if it loads all the virus def in memory won't that be > very RAM consuming? >
Not really. It you process say 2 mail simultaneously with clamscan, the 2 clamscan processes load the database into memory twice. If you process them with clamdscan, the single clamd has loaded the database only once, and shares that load with the two scanning processes/threads. It saves resources in the end game. You see: if you want to use clamav, the database has to be loaded in any case. With 1000 mails, clamscan loads the database 1000 times, clamd only once. _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
