<defunct> debugging routine?

[Julian Field]

At 01:47 16/05/2004, you wrote:
>It should be something extremely simple but I can not seem to find the
>answer. After the last upgrade of MailScanner
>on my server I get a <defunct> fork of Mailscanner after each processed
>batch. The scanner in general seems to work
>properly and I did not detect any mail loss, however this fact is still
>pretty annoying. I tried to figure out what is
>causing this, but I can not increase the verbosity of the log reporting. I
>tried to start mailscanner in debug mode,
>however the resulting information is almost identical to what you get
>while running in daemon mode. Essentially my
>question is how do I trace the whole process of receiving/scanning/sending.

Check your maillog for signs of error messages.
Is it actually processing mail successfully?
--
Julian Field
www.MailScanner.info
Professional Support Services at www.MailScanner.biz
MailScanner thanks transtec Computers for their support
PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654

-------------------------- MailScanner list ----------------------
To leave, send    leave mailscanner    to jiscmail at jiscmail.ac.uk
Before posting, please see the Most Asked Questions at
http://www.mailscanner.biz/maq/     and the archives at
http://www.jiscmail.ac.uk/lists/mailscanner.html