> 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.
[EMAIL PROTECTED]:/var/log/mail# mailq | grep 127.0.0.1 (connect to 127.0.0.1 [127.0.0.1]: read timeout) (connect to 127.0.0.1 [127.0.0.1]: read timeout) top: PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 10299 root 20 0 8288 8288 884 R 48.2 0.8 7:09.85 clamd 6731 root 18 0 8288 8288 884 R 46.3 0.8 20:32.06 clamd i think you are right. strange is, that as mailq says, these two mails are not mailing list digests, but ordinary emails... it is also strange, that now i have only 2 "broken" mails, usually, after one appears, the whole mailq is undeliverable... do you know any debug options i can use to debug these 2 mails? log in clamd.log says nothing thanks, jakub -- -- Jakub Suchy <[EMAIL PROTECTED]> -- LOGIOS s.r.o, V Podhájí 776/30, 400 01 Ústí nad Labem -- tel.: +420 474 745 159, fax: +420 474 745 160 -- e-mail: [EMAIL PROTECTED], web: http://www.logios.cz _______________________________________________ http://lurker.clamav.net/list/clamav-users.html
