I have rolled out clamd to a handful of Red Hat systems and they all seem to have high CPU usage when clamdscan runs at 2am. The rest of the day, clamd drops down to minimal usage. There isn't a lot of change on these systems so I can't imagine it's finding much, but it really pegs the CPU's. What configuration settings could I change for clamd or clamdscan to not hammer the CPU?
Thanks _______________________________________________ Help us build a comprehensive ClamAV guide: https://github.com/vrtadmin/clamav-faq http://www.clamav.net/contact.html#ml
