Single process taking over?
mailscanner at ecs.soton.ac.uk
Tue Feb 17 12:32:12 GMT 2004
At 11:38 17/02/2004, you wrote:
> > -----Original Message-----
> > From: MailScanner mailing list [mailto:MAILSCANNER at JISCMAIL.AC.UK] On
> > Behalf Of Julian Field
> > Sent: Tuesday, 17 February 2004 8:36 PM
> > To: MAILSCANNER at JISCMAIL.AC.UK
> > Subject: Re: Single process taking over?
> > Ah, a reproducible fault! I like those :-)
>I don't!! :)
> > What does your MailScanner.conf look like? (just the interesting bits,
> > don't care what all the filenames of your reports are and stuff like
> > that).
> > What virus scanner(s), SpamAssassin, etc?
>ClamAV, McAfee, Spamassassin 2.6.3, DCC, Razor
> > What is the last thing the runaway process logs before CPU hogging?
>Nothing abnormal, just the process starting and mail being processed, even
>in verbose logging, it just appears to be a normal process that won't let
>the other threads have any resources. If I kill it, the other threads spawn
>and run as per normal.
> > Does the CPU hogging start the instant you start MailScanner, or the
> > instant the first child process runs, or when?
>As soon as mail begins to be processed. If no mail is in the queue, not
>hogging, but the second any mail is in queue it's hogging.
>Max Children = 4
>Queue Scan Interval = 1
>MTA = sendmail
>Max Unscanned Bytes Per Scan = 100000000
>Max Unsafe Bytes Per Scan = 50000000
>Max Unscanned Messages Per Scan = 15
>Max Unsafe Messages Per Scan = 15
>Virus Scanning = yes
>Virus Scanners = mcafee clamav
>Virus Scanner Timeout = 300
>Spam Checks = yes
>Spam List =
>Use SpamAssassin = yes
>Max SpamAssassin Size = 90000
>Deliver In Background = yes
>Delivery Method = batch
>Let me know if you want any more detail..
One more thing. If you set "Debug = yes" and then kill the MailScanner
processes and run check_mailscanner once, what happens?
MailScanner thanks transtec Computers for their support
PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
More information about the MailScanner