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 <[email protected]> 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/752481
Title:
networking is not actually brought down/up when moving to/from
runlevel 1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/752481/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
