[Bug 752481] Re: networking is not actually brought down/up when moving to/from runlevel 1

Launchpad Bug Tracker 752481 at bugs.launchpad.net
Thu Sep 6 19:20:09 UTC 2012

This bug was fixed in the package ifupdown - 0.7.1ubuntu3

ifupdown (0.7.1ubuntu3) quantal; urgency=low

  * Add a 'stop on' rule for the networking service, so that we tear the
    network down at the correct point in the shutdown sequence (after remote
    filesystems have been unmounted).  This is mostly needed when using
    insserv upstart integration (not yet in Ubuntu) to ensure the shutdown
    doesn't hang waiting for an unsatisfiable init script dependency, but it
    also addresses the need for shutting down networking on runlevel changes
    - provided that umountnfs.sh itself is called for runlevel 1, which it
    currently is not.
  * Also start the job on runlevel [2345].  This is a no-op during a normal
    boot since the network will be started *before* runlevel is emitted, but
    is needed to restart the network after a change from runlevel 1.
    LP: #752481.
 -- Steve Langasek <steve.langasek at ubuntu.com>   Thu, 06 Sep 2012 15:05:32 -0400

** Changed in: ifupdown (Ubuntu)
       Status: Triaged => Fix Released

You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ifupdown in Ubuntu.

  networking is not actually brought down/up when moving to/from
  runlevel 1

Status in “ifupdown” package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: ifupdown

  Since the transition where networking has been handled largely by
  upstart, runlevel 1 does not bring down the network. Nor is it brought
  back up in any way by the transition back to runlevel 2.

To manage notifications about this bug go to:

More information about the foundations-bugs mailing list