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
