Well, I can prove the failure for
root # /usr/clamav/sbin/clamd --version
clamd / ClamAV version 20030806
selfbuilt with exim/exiscan 4.21.
one thread goes defunct, the master thread idles around and the third is
stuck in an empty event loop.
Exim connections pile up to (in this case: 777) connections and the mail
exchanger grinds down.
After killing clamd
stop)
pkill -9 -P 1 clamd && sleep 1 && echo 'Clam anti virus daemon stopped'
and waiting some additional time(!!!) it can be restarted
start)
rm -f /var/clamav/run/clamd
clamd && echo 'Clam anti virus daemon started'
Note the manual deletion of the socket. Bad bad bad bunny!
What exactly do You mean with "more robust against mail bodies"? There
should be no way to break the scanner with "bad mail". It should *protect*
other systems, not being exploitable(?) itself.
So, which version *is* stable?
You know:
- not leaking threads
- not leaking memory
- not leaking zombies
- not segfaulting...
- reliably restartable.
You want to know when You start to scan some million emails per day, what we
do here :-)
Yours sincerely
- Marian Eichholz
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Clamav-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/clamav-users
