[Bug 1061639] Re: Upstartification of /etc/init.d/networking has lost deconfiguring-networking event causing bad side-effects
Ernie 07
1061639 at bugs.launchpad.net
Fri Nov 2 02:44:58 UTC 2012
For my environment (Ethernet DSL to Internet) a temporary workaround
follows:
1. UNCHECK Enable Networking
2. Wait until after the disconnected message goes away
3. Restart and Shutdown
4. Fsck from an alternate installation will NOT throw any errors.
Apparently Unchecking Enable Networking does something that a simple
restart or shutdown does NOT in terms of preparing for a SAFE shutdown.
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1061639
Title:
Upstartification of /etc/init.d/networking has lost deconfiguring-
networking event causing bad side-effects
Status in “ifupdown” package in Ubuntu:
Fix Released
Status in “ifupdown” source package in Quantal:
Fix Released
Bug description:
In precise, /etc/init.d/networking was a true SysV service script that
did the following:
initctl emit deconfiguring-networking
In quantal, /etc/init.d/networking is now using the upstart-job
symlink back to the upstart job /etc/init/networking.conf.
The problem is that the 'deconfiguring-networking' is no longer being
emitted. This causes dbus to fail to stop on system shutdown which
causes a cascading effect whereby other Upstart jobs are also not shut
down. Eventually, the system halt with the message:
mount: / is busy
This results in a unclean shutdown which can result in FSCK being run
/ slow / bad user boot experience.
The two main options here are:
1) Re-instate the 'deconfiguring-networking' event.
2) Change the dbus 'stop on' condition and update upstart-events.7 to remove 'deconfiguring-networking'.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1061639/+subscriptions
More information about the foundations-bugs
mailing list