On Thu, 2004-03-18 at 07:30, adp wrote: > # /etc/rc.d/init.d/clamd stop > # /etc/rc.d/init.d/clamd start
> At that point mail started flowing again. > I think you'll find the blame lies with clamd. It has a history of hanging on certain messages. > I wish the log was more detailed. > Well, when a message has hung, the qmail-queue.log debug file would tell you where it was hanging, but you'd have to go through it line by line, looking to see where a message started to be processed, (and if I'm right) got to being passed to clamdscan. Then you'd probably see other new messages being processed and ending up being passed to the offender, and more new messages, etc, etc. At that stage you can diagnose that as the offender never appears to exit - that'd be why the timeout-killer kicks in later. > Is this clamd or spamd taking too long? > I'm guessing it's clamd 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: 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
