Well, the issue is that under normal traffic, I get around 5-15 clamscans running at same time. Then when one of the instances of clamscan messes up, the clamscans stack up and goes to 30-up to 180 one time I saw.
I know it won't help with the I/O that much but by being able to watch to see if there is a rogue process, then this would curb the heavy I/O.
I am trying to avoid the purchase of their anti-virus plugin but it seems that I won't be able to avoid it unless Process Tamer incorporates the CPU time watcher too.
The Clamscan randomly bogs up. There is no pattern to when it bogs up. Sometimes it works for days, sometimes just a few hours. Right now, I have it set to no more than 30 scan sessions yet if clamscan ends up in that endless loop, my mailserver self crashes itself and resets after 1 minute. However, the clamscan process is still running in the background at 100% CPU along with other dead clamscans from the previous mail server crash.
Now you see why this is necessary to monitor the CPU Time.
It is a security measure to ensure that my server does not become unresponsive.