[Bug 1061639] Re: Upstartification of /etc/init.d/networking has lost deconfiguring-networking event causing bad side-effects
Tue Bækgaard Holm
tueholm at gmail.com
Sat Feb 23 15:28:05 UTC 2013
Finally found a workaround, Yotas fix (#21) seemed to work fine for the
time consumed shutting the system down, but i still got the bug.
Eventually I found out that it only happened when I was connected to a
network, so I made a small script which shuts down my network interfaces
when my computer shuts down, and this did the trick.
Simply put I created: "/etc/init.d/nw.sh"
Containing: "ifconfig <interface> down" for all my physical network
interfaces.
Then as root:
ln /etc/init.d/nw.sh /etc/rc0.d/K10nw.sh
ln /etc/init.d/nw.sh /etc/rc6.d/K10nw.sh
And bam! My computer was suddenly able to shut down. Hopes this helps.
--
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