spamd: handled cleanup of child pid 19888 due to SIGCHLD
spamd[5262]: prefork: child states: II

I see a lot of mention of these messages showing up in 3.1, but I have
not seen a definitive answer as to if I need to pay more attention to
them or they are just a minor/visual annoyance in the logs and will be
cleaned up with a patch or the next release.

It's log noise. Nothing to be alarmed about. By default, 3.1 keeps two child processes running, and one as a spare. If it's processing two messages at a time, it will start up another child as a spare. It will keep doing that until you've hit the max-children setting. When there's more than two idle processes again, it will kill them off until there's only two. That's what you're seeing.

Reply via email to