Since upgrading to the new spamassassin, I'm seeing the following two
log entries related to cleanup of child PIDs:

1. Apr  1 08:26:38 spamd2 spamd[396]: spamd: handled cleanup of child
pid [31720] due to SIGCHLD: INTERRUPTED, signal 2 (0002)

2. Mar 28 18:00:15 spamd2 spamd[17562]: spamd: handled cleanup of child
pid [391] due to SIGCHLD: exit 0

If I were to guess, the second one seems to be when things are acting
right, the first one seems problematic, and I'm trying to determine what
causes it. The logs for that process aren't particularly interesting,
they are just like any others, with various prefork childstate entries:

Mar 28 06:25:35 spamd2 spamd[396]: prefork: child states: II
Mar 28 06:25:36 spamd2 spamd[396]: prefork: child states: IB

but nothing particularly egregious looking. 

Can someone help me clarify what causes an INTERRUPTED signal? Should I
worry about it? Should I ignore it in logcheck?

thanks!
micah



-- 
"It is no measure of health to be well adjusted to a profoundly sick society." 
- J Krishnamurti 

Reply via email to