On Jan 14, 11:43am, "David F. Skoll" wrote:
} Nels Lindquist wrote:
}
} >>Aug 24 09:26:33 aerodrome mimedefang-multiplexor[32444]: Slave 7 (pid
} >>680) taking way too long to exit; sending SIGKILL
}
} > After the SIGKILL the process stays in a zombie state until
} > MIMEDefang is restarted.
}
} Ah, well. If SIGKILL won't kill it, then something very bad is
} happening. I've only seen that happen when something is stuck in
} a disk-wait state, or in a state where it's trying to open some kind
} of device like a printer or tape drive, and is stuck somewhere deep in
} the kernel.
It would also happen if the parent doesn't call waitx(2) to reap
it. That the processes go away when mimedefang is killed points in
this direction since this means that the processes would be reparented
to init(8) when their parent is killed and init(8) is always
wait(2)ing. The question now is whether mimedefang is failing to reap
them and if so, why?
}-- End of excerpt from "David F. Skoll"
_______________________________________________
Visit http://www.mimedefang.org and http://www.roaringpenguin.com
MIMEDefang mailing list
[email protected]
http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
