Ubuntu
insserv package

  1. Bug #858122
  2. Comment #8

Comment 8 for bug 858122

Revision history for this message
Steve Langasek (vorlon) wrote : Re: [Bug 858122] Re: incomplete migration to /run

On Tue, Sep 27, 2011 at 05:51:33PM -0000, Tom Chiverton wrote:

> lrwxrwxrwx 1 root root 22 2010-09-26 10:08 K08umountnfs.sh -> ../init.d/umountnfs.sh
[...]
> lrwxrwxrwx 1 root root 16 2009-11-23 21:38 S01reboot -> ../init.d/reboot
> lrwxrwxrwx 1 root root 18 2009-11-23 21:38 S01sendsigs -> ../init.d/sendsigs
> lrwxrwxrwx 1 root root 18 2009-11-23 21:38 S01umountfs -> ../init.d/umountfs
> lrwxrwxrwx 1 root root 20 2009-11-23 21:38 S01umountroot -> ../init.d/umountroot

Aha, here's the problem! This is certainly not the order in which these
scripts are supposed to be run. I'm surprised you didn't encounter serious
problems before now, given the above... your system is configured to reboot
before (or in parallel with) cleanly shutting down processes and unmounting
filesystems. So /etc/init.d/umountroot never gets a chance to run, or if it
does things are still mounted at the time!

Does the file /etc/init.d/.legacy-bootordering exist on your system? If
not, it looks like something has happened to fail to block insserv from
rearranging your symlinks. Did you make any deliberate changes to your
system involving insserv? How was this system originally installed?

Here are the correct symlinks on an oneiric system:

lrwxrwxrwx 1 root root 18 Apr 30 2009 S20sendsigs -> ../init.d/sendsigs
lrwxrwxrwx 1 root root 17 Apr 30 2009 S30urandom -> ../init.d/urandom
lrwxrwxrwx 1 root root 22 Apr 30 2009 S31umountnfs.sh -> ../init.d/umountnfs.sh
lrwxrwxrwx 1 root root 20 Jun 9 05:43 S35networking -> ../init.d/networking
lrwxrwxrwx 1 root root 18 Apr 30 2009 S40umountfs -> ../init.d/umountfs
lrwxrwxrwx 1 root root 20 Apr 30 2009 S60umountroot -> ../init.d/umountroot
lrwxrwxrwx 1 root root 16 Apr 30 2009 S90reboot -> ../init.d/reboot

I don't know if there's a good way to undo insserv mangling automatically,
or if you'll need to adjust these by hand.

Opening a task on sysv-rc, which is supposed to ensure that
/etc/init.d/.legacy-bootordering exists.

--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://www.debian.org/
<email address hidden> <email address hidden>