[Pkg-sysvinit-devel] Bug#582442: Bug#582442: sysvinit: Failing to interrupt some script after upgrade

Henrique de Moraes Holschuh hmh at debian.org
Sun May 23 03:36:20 UTC 2010

On Thu, 20 May 2010, Petter Reinholdtsen wrote:
> [Matthieu Castet]
> > I interrupt sometimes fsck (when I don't want to wait), now this
> > doesn't work.
> Wow.  You are braver than me.  I never considered that use case. :)

It is quite common.  Interrupting fsck if it is not in repair mode is safe,
and common.

SIGINT'ing the dhcp-client is also common.

Break that, and you will have a lot of people out after our blood...

Basically, if someone wants to ^C something, let them.

> The parallel starting is done by by startpar, so I guess that is the
> program that need to be adjusted.

Yeah. But how?  SIGINT, SIGTERM and SIGQUIT must be DWIM (do what I mean) in
a parallel boot scenario...  probably the best we can do is to have startpar
send the signal to all its children, and if it gets repeated signals in a
row [say, before it gets any SIGCHILD back], have it die.

  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh

More information about the Pkg-sysvinit-devel mailing list