sendsigs should not start usplash_down

Bug #277058 reported by Matt Zimmerman on 2008-10-02
Affects Status Importance Assigned to Milestone
sysvinit (Ubuntu)
Matt Zimmerman
Matt Zimmerman

Bug Description

Binary package hint: sysvinit

/etc/init.d/sendsigs currently has this code:

 if which usplash_down >/dev/null; then

If usplash_down is already running at this point, this should not be done, as the sendsigs.omit stuff should prevent it from being killed.

If usplash_down is NOT already running at this point, there is really no point in starting it, because the system shuts down about one second later.

Therefore, I think this code should be removed entirely.

Related branches

Matt Zimmerman (mdz) on 2008-10-02
Changed in sysvinit:
importance: Undecided → Medium
status: New → Triaged
Matt Zimmerman (mdz) wrote :

I've prepared a debdiff for this

Changed in sysvinit:
assignee: nobody → mdz
status: Triaged → In Progress
Matt Zimmerman (mdz) wrote :
Martin Pitt (pitti) wrote :

Thanks Matt, uploaded.

Changed in sysvinit:
status: In Progress → Fix Committed
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package sysvinit - 2.86.ds1-59ubuntu11

sysvinit (2.86.ds1-59ubuntu11) intrepid; urgency=low

  * sendsigs: Don't call usplash_down anymore. This was a holdover from when
    usplash was being killed by this script. Now, usplash_down should be
    already running by this point, and if it isn't, there's no point in
    starting it (LP: #277058)

 -- Matt Zimmerman <email address hidden> Thu, 02 Oct 2008 11:31:01 +0100

Changed in sysvinit:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers