Jason Haar wrote: > Tomasz Kojm wrote: > >>> I use ClamAV in association with qmailscanner and SpamAssassin to >>> filter email. Several times in the past three days this mail server >>> has become unresponsive. The only things that I can think of that >>> has changed in that time are the virus definitions used by Clam. >>> ps -A | grep clamscan| wc -l reports many more processes than ps -A >>> | grep qmail-smtpd | wc-l, leading me to believe that clamscan is >>> sometimes not returning and the processes are, in effect, becoming >>> defunct. Is there any sense to this hypothesis? Any other ideas >>> of what is going on? Program versions are listed below. >>> >>> >> >> What is a value of softlimit? >> >> >> > More to the point - why are you using clamscan instead of clamdscan? > There is no good reason I'm aware of to EVER use clamscan over > clamdscan on a mail server.
I'm using clamscan because I have had reliability issues with clamdscan. They may have been resolved now, but when I was using clamd/clamdscan the smtp service would quit working after a while. As we don't do too high a volume of mail clamscan has performed adequately. --TWH _______________________________________________ http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
