Children dying and not being replaced

[Julian Field]

I fixed this in a recent release. Not 100% sure when, but the ChangeLog for
4.13 mentions improvements to child process handling.

At 16:24 11/08/2003, you wrote:
>Twice in the last few days we've had a situation here in which a child dies
>of old age and is not replaced. We should be running 5 children at all
>times, but it drops to 3 which massively slows down processing. After a
>mailscanner restart, of course, everything is fine. Logs show nothing
>unusual:
>
>Aug 11 05:54:06 external-smtp MailScanner[29357]: Config: calling custom end
>fun
>ction SQLLogging
>Aug 11 05:54:06 external-smtp MailScanner[29357]: Ending SQL Logging temp
>output
>  and flushing to database
>Aug 11 05:54:24 external-smtp MailScanner[29357]: Database flush completed
>Aug 11 05:54:24 external-smtp MailScanner[29357]: MailScanner child dying of
>old
>  age
>
>Is there anything in particular I should be looking for to determine the
>cause?
>
>Andrew Magnusson
>Internet Product Analyst
>COCC
>1-877-678-0444 extension 640
>
>
>
>--
>*** This message originates from COCC, Inc.
>
>If the reader of this message, regardless of the address or routing, is
>not an intended recipient, you are hereby notified that you have received
>this transmittal in error and any review; use, distribution, dissemination
>or copying is strictly prohibited.  If you have received this message in
>error, please delete this e-mail and all files transmitted with it from
>your system and immediately notify COCC, Inc. by sending reply e-mail to
>the sender of this message.
>
>Thank you. ***

--
Julian Field
www.MailScanner.info
Professional Support Services at www.MailScanner.biz
MailScanner thanks transtec Computers for their support