<defunct> debugging routine?

[Peter Rabbitson]

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.

Thanks

Peter

-------------------------- 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