(In reply to Simon McVittie from comment #6) > Unfortunately, "systemctl restart dbus" (which was never supported either) > will now start a second dbus-daemon in parallel with the first
I think that's unacceptable. (In reply to Lennart Poettering from comment #12) > If at all, use RefuseManualStop=yes on the unit, but I don't like that much > either. I don't think this would satisfy the original requirement unless the ExecStop=/bin/true was also included, and you've said that that's undesired. > Please do not apply that ExecStop= thing. You really shouldn't block that. Fair enough. NOTOURBUG then. > The best way is to fix the few services that really need dbus > unconditionally to be around to add After=dbus.service. And all is good. OK. In the case of the original bug report, I think this means wpasupplicant and maybe NetworkManager would have to either turn off exit-on-disconnect (for libdbus and/or GDBus, depending which they use), or be After=dbus.service. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1438612 Title: remote file systems hang on shutdown, D-BUS stops too early To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1438612/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
