Comment 44 for bug 13405

Message-ID: <email address hidden>
Date: Sun, 27 Mar 2005 23:38:47 +0200
From: Marc Haber <email address hidden>
To: Frans Pop <email address hidden>
Cc: <email address hidden>, <email address hidden>
Subject: Re: Long pause when exim daemon is being stopped (was: Re: exim4 prone to break d-i,
 bug #297607)

Ok. We are nearing the goal now.

On Sun, Mar 27, 2005 at 11:10:12PM +0200, Frans Pop wrote:
> On Sunday 27 March 2005 19:47, Marc Haber wrote:
> > An strace of start-stop-daemon and the exim daemon with timestamps
> > enabled would be nice.
> >
> OK. Here's the last piece of the puzzle. The strace for the daemon gives:
> Process 7475 attached - interrupt to quit
> 21:04:29.883761 select(1, [0], NULL, NULL, NULL) = ? ERESTARTNOHAND (To be restarted)
> 21:04:40.296456 --- SIGTERM (Terminated) @ 0 (0) ---
> 21:04:40.297103 select(1, [0], NULL, NULL, NULL) = ? ERESTARTNOHAND (To be restarted)
> 21:04:50.309359 +++ killed by SIGKILL +++
>
> The pause is clearly visible in the timings between the last 2 lines.

How does that strace look like in a situation where the daemon
immediately dies?

When I tried to reproduce, I once accidentally started base-config in
an strace, and was unable to kill the base-config process with Ctrl-C
which _usually_ works.

Is it possible that the installer establishes a signal handler which
is then inherited by the processes started from the installer, and
thus the SIGTERM sent by s-s-d to exim is caught by that handler
instead of getting through to exim?

Greetings
Marc

--
-----------------------------------------------------------------------------
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Mannheim, Germany | lose things." Winona Ryder | Fon: *49 621 72739834
Nordisch by Nature | How to make an American Quilt | Fax: *49 621 72739835