Comment 43 for bug 1072518

Revision history for this message
Dimitri John Ledkov (xnox) wrote :

@ ivan-kukobko
This "sudo service network-manager restart" does not crash dbus.
This "sudo service network-interface restart" makes no-sense, as no instance is specified and it's an instance job.

Please file separate, new bugs for any issues that you have. And let developers responsible for these component to triage them appropriately.

@ bgonza868
Read the job, and look at the events. As it stands now, stopping (or restarting networking service) is intended to only happen during shutdown. As all network interfaces are deconfigured, all network filesystems are unmounted, system dbus is stopped, all graphical user sessions are killed, network-manager/bluetooth/avahi/ofono are all stopped. This is why networking job is only supported to be started on boot, and stopped on shutdown. There is no logic to support interactive stopping or restarting this job in Ubuntu. This has nothing to do with freedesktop, other operating systems, other upstream projects, syvinit, upstart or systemd. This is purely what networking.conf upstart job supports doing as shipped in the ifupdown package in ubuntu today.