On 10.02.16 05:29, 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?
For the case of any bug in clamd, it should not be able to scan private
files.
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?
clamscan is not the preferred way. There are cases where clamscan is better.
However: how many infections are there for linux system that you want to
scan it all? The most common usage of clamav is to scan mail going through
system and scan filesystems shared to windows machines.
--
Matus UHLAR - fantomas, [email protected] ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
I wonder how much deeper the ocean would be without sponges.
_______________________________________________
Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq
http://www.clamav.net/contact.html#ml
