Jakub Suchy wrote:
now we tried to debug clamav again and started it and it works...It's really strange, because we didn't changed anything in configuration. Is it possible, that the problem was caused by some malicious mail in mailq?
No, it's probably the first reason given by Stephen: long mail list digests make clamdscan 0.83 fall into a loop.
When that happens clamscan/clamdscan grab the CPU and you can easily see them as the problem. The solution, as Stephen said, is to use a more recent version from CVS.
Regards. -- Ren� Berber
_______________________________________________ http://lurker.clamav.net/list/clamav-users.html
