Upstartification of /etc/init.d/networking has lost deconfiguring-networking event causing bad side-effects
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ifupdown (Ubuntu) |
Fix Released
|
High
|
Stéphane Graber | ||
Quantal |
Fix Released
|
High
|
Stéphane Graber |
Bug Description
In precise, /etc/init.
initctl emit deconfiguring-
In quantal, /etc/init.
The problem is that the 'deconfiguring-
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-
2) Change the dbus 'stop on' condition and update upstart-events.7 to remove 'deconfiguring-
Related branches
Changed in ifupdown (Ubuntu): | |
importance: | Undecided → High |
Changed in ifupdown (Ubuntu Quantal): | |
status: | Triaged → In Progress |
Stéphane, this is a regression in the latest upload that needs to be fixed for release. Thanks!