Bug#297607: Long pause when exim daemon is being stopped (was: Re: exim4 prone to break d-i, bug #297607)

[Marc Haber]

On Mon, Mar 28, 2005 at 03:52:00PM +0300, Eugeniy Meshcheryakov wrote:
> 28.03.2005 ?? 00:21 +0200 Frans Pop ??????????????(-????):
> > > 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?
> > 
> > Could well be. /usr/sbin/base-config has:
> > 
> > <snip>
> > if [ "$NEW" ]; then
> >         # Trap most signals because a ctrl-c killing base-config
> >         # in the middle of the second stage install would be bad.
> >         trap "" HUP INT QUIT TERM
> > 
> >         [some lines not included]
> > else
> >         # Running again on an existing install. Just trap ctrl-c, and
> >         # cleanly exit.
> >         trap cleanup INT
> > fi
> > </snip>
> > 
> 
> Here is part of diff of contents of /proc/$PID/status files for exim run
> form command line and from base-config:
> 
> 24c24
> < SigIgn:       0000000000001000
> ---
> > SigIgn:       0000000000005006
> 
> Those new ignored signals are INT (2+1), QUIT (3+1) and TERM (14+1).

So exim is configured by base-config to ignore SIGTERM? No wonder that
it wouldn't die.

I'd call that a base-config issue.

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