[EMAIL PROTECTED] wrote: [...]
> Would it be possible for you to give me an explanation of how you're > running clamav under supervise? I have most everything else running that > way, and I'd much prefer to have clamav run that way as well - I just > haven't had time to work through that one. Absolutely. I wrote a howto for this back in Sep 2003 that seems to have been adopted by the ClamAV project. You can find it here: http://www.clamav.net/doc/0.70/clamd_supervised/clamd-daemontools-guide.txt I wrote it for ClamAV 0.60 (which is what my production server runs currently). However, 0.60 is pretty ancient now and doesn't handle binhex encoding, so I plan to upgrade to either 0.68-1 or 0.70-rc1 today or tommorrow. I'll be sure to update and resubmit the doc if anything notable has changed. >>> It seems like it would be more reasonable for the scan process to go >>> 'Process can't work!' and then either feed the mails through (maybe with >>> a >>> message to the admin that the program is buggering up), or store them in >>> queue, again, with a message to the admin. >> >> I'd rather not send my users viruses, personally. I think it would be >> sufficient >> for qmail-scanner to cause qmail-smtpd to return a 451 code. This way the >> remote >> sending mail server would queue the message and try again later. >> >> My question would be: Does qmail-scanner cause qmail-smtpd to return a >> 451 if it >> detects problems with one of it's scanners? Does it email the admin in >> this case? >> > > Honestly - I'm not sure. I found that SOME of the emails DID get > requeued, but certainly not all of them. (not judging by the size of my > incoming mail logs.) Well, I'm sure Jason Haar knows. Jason? > And clamd blew up again last night with no notice - I'm going to upgrade > ClamAV, and see if that fixes the problem. I've already upped the > QMAILQUEUE softlimit - again. Yeah, I highly recommend daemontools for any long running program. Even if it only dies once a year, daemontools will save you a world of trouble. The trick is to make sure it completely dies, and doesn't just HANG. :) daemontools can't really help you if your software is running but unresponsive. > If it happens once more, I guess I'll replace the memory in the box - it's > just strange that it is only ClamAV in conjunction with qmail-scanner (but > ClamAV is outside the scope of this list) ClamAV has a long history of crashing. I personally don't hold that fact against it. ClamAV is great software! Just make sure you run it with daemontools or something similar. -- Jesse Guardiani, Systems Administrator WingNET Internet Services, P.O. Box 2605 // Cleveland, TN 37320-2605 423-559-LINK (v) 423-559-5145 (f) http://www.wingnet.net ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Qmail-scanner-general mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/qmail-scanner-general
