Thomas Haller bf54a5bfba systemd: add "After=dbus.service" to NetworkManager.service ... Order NetworkManager after dbus. Otherwise during shutdown, both service are killed together and possibly NetworkManager can no longer use D-Bus during shutdown. It will need it however to communicate with VPN plugins and wpa-supplicant. Related: https://bugs.freedesktop.org/show_bug.cgi?id=89847#c14 Related: https://bugzilla.redhat.com/show_bug.cgi?id=1214466		2016-01-21 11:01:36 +01:00
..
84-nm-drivers.rules	Split out the bits which determine ID_NET_DRIVER or DRIVERS into separate udev rules file	2015-08-31 22:41:17 +02:00
85-nm-unmanaged.rules	Split out the bits which determine ID_NET_DRIVER or DRIVERS into separate udev rules file	2015-08-31 22:41:17 +02:00
Makefile.am	Split out the bits which determine ID_NET_DRIVER or DRIVERS into separate udev rules file	2015-08-31 22:41:17 +02:00
NetworkManager-dispatcher.service.in	dispatcher: rename executable to 'nm-dispatcher'	2014-06-06 13:43:45 -05:00
NetworkManager-wait-online-systemd-pre200.service.in	systemd: update NetworkManager-wait-online.service to wait for startup	2014-03-31 08:37:10 +02:00
NetworkManager-wait-online.service.in	systemd: stop blocking network.target in NetworkManager-wait-online.service	2015-10-30 11:37:09 +01:00
NetworkManager.service.in	systemd: add "After=dbus.service" to NetworkManager.service	2016-01-21 11:01:36 +01:00
org.freedesktop.NetworkManager.service.in	core: more systemd service file fixes	2010-08-18 17:01:26 -05:00
server.conf.in	core: change the rules for ignore-carrier	2013-07-22 11:30:21 -04:00