Jason Haar wrote:
I really should just drop support for clamscan. There is *never* a good
reason to use it!!!
Figure out how to use clamd, and re-run Qmail-Scanner ./configure to
detect and use clamdscan instead of clamscan.
Also ensure you are running the current release of ClamAV, and also
check Google as I think you implied you are using 64bit Linux? Maybe
there are bugs with clamscan WRT 64bit?
Hi,
Thanks for the support from everyone. I have solved the problem. I did
an strace of one of the running clamscan processes after it had been
going for like 20 minutes CPU time, and it was getting lots of
out-of-memory errors, but not giving up. Stupidly, I didn't keep the
exact error messages. I upped the memory allowed to qmail-smtpd from
25000000 to 50000000 and I haven't seen the problem since. (I am not
running in 64 bit mode, precisely to avoid weird issues like you suggest.)
The reason that I have chosen clamscan rather than the clamdscan is that
I prefer not to have services running if I don't have to, in case of
memory leaks or hackability-issues or something like that. Are these
arguments broken (since you say there's never a good reason to use
clamscan)?
Cheers,
Ketil Froyn
[EMAIL PROTECTED]
http://ketil.froyn.name/
-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc. Get Certified Today
Register for a JBoss Training Course. Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click
_______________________________________________
Qmail-scanner-general mailing list
Qmail-scanner-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qmail-scanner-general
