[clamav-users] Clamd vs clamscan

[Dennis Peterson]

Clamd is for on-demand scanning and purpose built for email scanning. It runs as 
an unprivileged user which makes it awkward for scanning arbitrary files. 
Clamscan is for user initiated or scheduled scanning of arbitrary files, and can 
be run as any system user. Clamscan is undesirable as an on-demand scanner owing 
to startup delays while it loads signature files. Each utility has a well 
thought out role and when used as intended it provides an excellent and 
efficient service.

dp

On 2/10/16 2:29 AM, Brad Scalio wrote:
> I've seen a lot of fodder on clamd vs clamscan, running 0.99 on RHEL6.7
> exit/entry points ... While it's easy enough to use clamscan via cron, is
> there any good stepwise SOP on getting clamd to work permission wise to
> scan all filesystem?  I like the ability to have it all controlled via the
> daemon, easier to enforce configurations via puppet, easier quick checking
> and tweaking of conf, etc ... Apologies if I missed the page or doc, but
> been googling for months to find a simple guide.
>
> If clamscan is the preferred way, I'm fine with that, just not sure why
> there's a daemon then?  Is it for on-access, more for other OS installs?
>
> Thanks!
> Brad
> _______________________________________________
> Help us build a comprehensive ClamAV guide:
> https://github.com/vrtadmin/clamav-faq
>
> http://www.clamav.net/contact.html#ml