[Bug 863864] [NEW] /etc/init/failsafe.conf doesn't actually stop on runlevel

[Steve Langasek]

Public bug reported:

The failsafe job is meant to inform the user that the system is waiting
for the network to come up, and start the runlevel if a timeout is
reached.

However, the 'stop on runlevel' does *not* work as designed, because all
the activity here is done in the pre-start script which upstart will not
kill when the job target changes to stop:

$ sudo start failsafe&
[1] 3979
vorlon at nvidia-8600m:~$ status failsafe
failsafe start/pre-start, process 3981
vorlon at nvidia-8600m:~$ sudo stop failsafe&
[2] 3985
vorlon at nvidia-8600m:~$ status failsafefailsafe stop/pre-start, process 3981

failsafe stop/pre-start, process 3981
[1]-  Done                    sudo start failsafe

So the pre-start script continues sleeping, and continues sending
messages to plymouth.

If you happen to reboot the system within two minutes of startup, this
results in the messages being printed on the splash screen at
*shutdown*, which is rather confusing.

To avoid this, I think the failsafe job should be switched to do its
work in 'script' instead of 'pre-start script', and rc-sysinit changed
to listen for an event emitted by the failsafe job at the end of this
script instead of on 'started failsafe'.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: upstart 1.3-0ubuntu9
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu2
Architecture: amd64
Date: Sat Oct  1 00:02:54 2011
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100406.1)
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: upstart
UpgradeStatus: Upgraded to oneiric on 2011-09-23 (7 days ago)
modified.conffile..etc.init.tty2.conf: [modified]
mtime.conffile..etc.init.tty2.conf: 2010-04-18T00:37:33.806038

** Affects: upstart (Ubuntu)
     Importance: Medium
         Status: Triaged


** Tags: amd64 apport-bug oneiric running-unity

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

Title:
  /etc/init/failsafe.conf doesn't actually stop on runlevel

Status in “upstart” package in Ubuntu:
  Triaged

Bug description:
  The failsafe job is meant to inform the user that the system is
  waiting for the network to come up, and start the runlevel if a
  timeout is reached.

  However, the 'stop on runlevel' does *not* work as designed, because
  all the activity here is done in the pre-start script which upstart
  will not kill when the job target changes to stop:

  $ sudo start failsafe&
  [1] 3979
  vorlon at nvidia-8600m:~$ status failsafe
  failsafe start/pre-start, process 3981
  vorlon at nvidia-8600m:~$ sudo stop failsafe&
  [2] 3985
  vorlon at nvidia-8600m:~$ status failsafefailsafe stop/pre-start, process 3981

  failsafe stop/pre-start, process 3981
  [1]-  Done                    sudo start failsafe

  So the pre-start script continues sleeping, and continues sending
  messages to plymouth.

  If you happen to reboot the system within two minutes of startup, this
  results in the messages being printed on the splash screen at
  *shutdown*, which is rather confusing.

  To avoid this, I think the failsafe job should be switched to do its
  work in 'script' instead of 'pre-start script', and rc-sysinit changed
  to listen for an event emitted by the failsafe job at the end of this
  script instead of on 'started failsafe'.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: upstart 1.3-0ubuntu9
  ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu2
  Architecture: amd64
  Date: Sat Oct  1 00:02:54 2011
  InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100406.1)
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: upstart
  UpgradeStatus: Upgraded to oneiric on 2011-09-23 (7 days ago)
  modified.conffile..etc.init.tty2.conf: [modified]
  mtime.conffile..etc.init.tty2.conf: 2010-04-18T00:37:33.806038

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/863864/+subscriptions