ingle core. There is
> no way
> around the disk IO problem because it scans files. But - if you run it just
> after a system backup chances are good it will find many of the files it
> scans
> in cache. That helps reduce disk IO but bumps up CPU load.
>
> dp
>
>
> On 1/
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
