[Bug 1061639] Re: Upstartification of /etc/init.d/networking has lost deconfiguring-networking event causing bad side-effects

[yota]

Thank you Marius!

Yes, modem-manager was causing a significant part (but not all) of the
shutdown delay, I'll post my findings about it in the relative bug
report.

Still I believe that ifupdown could handle dhclient and/or dnsmasq that
were keeping / busy.

-- 
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