[Bug 858122] Re: incomplete migration to /run (shutdown script order has been demolished)

[Steve Langasek]

On Fri, Jan 13, 2012 at 08:42:12AM -0000, Adam Stokes wrote:
> If we think about moving insserv out of system path we need to make sure
> that update-rc.d is not broken by this since it assumes it can reach the
> binary within the path.  Other than that I dont think anything else
> would be affected.

In fact, update-rc.d only ever calls insserv if
/etc/init.d/.legacy-bootordering does not exist, which it should for all
Ubuntu systems:

if ( ! -f "/etc/init.d/.legacy-bootordering" ) {
    info("using dependency based boot sequencing");
    exit insserv_updatercd(@ARGV);
}

Having update-rc.d fail for users who have manually removed this file is
probably the lesser evil, and fixable by having them re-create the flag
file.

-- 
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/
slangasek at ubuntu.com                                     vorlon at debian.org

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to sysvinit in Ubuntu.
https://bugs.launchpad.net/bugs/858122

Title:
  incomplete migration to /run (shutdown script order has been
  demolished)

Status in Release Notes for Ubuntu:
  Fix Released
Status in “sysvinit” package in Ubuntu:
  Triaged
Status in “sysvinit” source package in Oneiric:
  Triaged
Status in “sysvinit” source package in Precise:
  Triaged

Bug description:
  I had the exact same issue documented as
  https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/807306
  on upgrade from 11.04 to 11.10. Opening new bug as req.

  Removing the existing /var/run and /var/run/lock and replacing with
  sym links as per comment 76 there fixed it.

  The impact of this was a total lack of system (wireless) networking
  coming up - this gives a >! minute pause during boot, as well as a
  subsequent total failure to be able to log into X (KDE or GNOME
  sessions give a cryptic error related to DBUS).

  I've just run an apt-get update/upgrade after *finally* getting back
  into my new 11.10 beta 2 system, and no updates to the mountall show
  up... therefore I assume this bug is still present.

  To correct the broken symlinks, run the following commands as root:
   mv /etc/rc6.d/S*reboot /etc/rc6.d/S90reboot
   mv /etc/rc6.d/S*umountroot /etc/rc6.d/S60umountroot
   mv /etc/rc6.d/S*umountnfs.sh /etc/rc6.d/S31umountnfs.sh
   mv /etc/rc6.d/S*umountfs /etc/rc6.d/S40umountfs
   mv /etc/rc6.d/S*sendsigs /etc/rc6.d/S20sendsigs

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: initscripts 2.88dsf-13.10ubuntu4
  ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
  Uname: Linux 3.0.0-11-generic i686
  ApportVersion: 1.23-0ubuntu1
  Architecture: i386
  Date: Sat Sep 24 10:49:58 2011
  ProcEnviron:
   LANGUAGE=
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: sysvinit
  UpgradeStatus: Upgraded to oneiric on 2011-09-23 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/858122/+subscriptions