Hi there I am running clamd under daemontools, with softlimit to limit the amount of memory clamd can grow to.
I upgraded to 0.65 from a (much) older release, and ran into all sorts of problems. Basically it would run fine for a while, and then clamd would die in such a fashion that it was still hanging around, and all future clamdscan calls would hang, waiting for clamd to do something. In the end I found it was due to clamd needing to grow >20M RAM (this is under RH 8). I upped softlimit to 30M and it appears fine again. (it's to do with the file size - small files - small memory, large file - bang!) I turned on debugging via clamav.conf, and what happened when clamd ran out of memory is that it reported "Unexpected error.", and then ps would show this zombie process "[clamd <defunct>]". At this stage clamdscan stops working. I've gone back and forth between 20 and 30M, and can repeat this every time. BTW: shouldn't clamdscan have some form of sanity check whereby it'll exit if it doesn't hear from clamd after some time? Maybe if clamd would guarantee to send dots or something every 5 secs, then after (say) 15 secs, clamdscan could exit with something like "clamd is down" error? Cheers Jason Haar Information Security Manager, Trimble Navigation Ltd. Phone: +64 3 9635 377 Fax: +64 3 9635 417 PGP Fingerprint: 7A2E 0407 C9A6 CAF6 2B9F 8422 C063 5EBB FE1D 66D1 ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Clamav-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/clamav-users
