On So, 05 Aug 2007, I wrote:
> On the problematic system openssh had been restarted from a
> process with SIGALRM blocked though. Don't know how that happened
> initially, but now (through long running screen sessions etc.)
> the system is tainted with many processes that have
> 0000000000002000 set in the SigBlk: field of /proc/PID/status.
>
> Strange, that no other problems resulted (or at least haven't
> been recognized).
>
> Anyway - no Exim topic.
Thinking a little bit more about it: maybe it is.
Signal handling in different POSIX OSes seems to be
difficult, but why is Exim not unblocking SIGALRM with
sigprocmask in daemon.c to guard against such a problem?
Lutz
--
Lutz Preßler <Lutz.Pressler@???> http://www.SerNet.DE/
SerNet Service Network GmbH, Bahnhofsallee 1b, D-37081 Göttingen
Tel.: +49-551-370000-2, FAX: +49-551-370000-9
AG Göttingen, HRB 2816, GF: Dr. Johannes Loxen
