NetworkManager/data/NetworkManager.service.in

[Unit]
Description=Network Manager
Wants=network.target
Before=network.target

[Service]
Type=dbus
BusName=org.freedesktop.NetworkManager
ExecStart=@sbindir@/NetworkManager --no-daemon
# NM doesn't want systemd to kill its children for it
KillMode=process

[Install]
WantedBy=multi-user.target
Alias=dbus-org.freedesktop.NetworkManager.service
Also=NetworkManager-dispatcher.service
core: add systemd unit support 2010-08-12 11:15:26 -05:00			`[Unit]`
			`Description=Network Manager`
systemd: pull in network.service and introduce NetworkManager-wait-online.service This pulls in network.target from NetworkManager.service (and not the other way round), as suggested and agreed on on the systemd ML: http://lists.freedesktop.org/archives/systemd-devel/2011-March/001692.html This also introduces an auxiliary service NetworkManager-wait-online.service that can be used to order a unit after the point where the network is available. When this is enabled with "systemd enable NetworkManager-wait-online.service" the unit network.target will be delayed until the network is up, which is suitable for synchronizing NFS mounts and similar to it. https://bugzilla.redhat.com/show_bug.cgi?id=692008 2011-04-06 04:30:02 +02:00			`Wants=network.target`
			`Before=network.target`
core: add systemd unit support 2010-08-12 11:15:26 -05:00
			`[Service]`
			`Type=dbus`
			`BusName=org.freedesktop.NetworkManager`
			`ExecStart=@sbindir@/NetworkManager --no-daemon`
systemd: set KillMode=process By default, when shutting NM down, systemd will kill everything in its cgroup. But this can cause problems (eg, NM thinking that dhclient crashed and then taking down an interface that it would otherwise have left up). Fix this by setting KillMode=process, which tells systemd to only kill NM itself, and let NM kill its children. https://bugzilla.redhat.com/show_bug.cgi?id=876218 2013-01-04 11:53:03 -05:00			`# NM doesn't want systemd to kill its children for it`
			`KillMode=process`
core: add systemd unit support 2010-08-12 11:15:26 -05:00
			`[Install]`
systemd: pull in network.service and introduce NetworkManager-wait-online.service This pulls in network.target from NetworkManager.service (and not the other way round), as suggested and agreed on on the systemd ML: http://lists.freedesktop.org/archives/systemd-devel/2011-March/001692.html This also introduces an auxiliary service NetworkManager-wait-online.service that can be used to order a unit after the point where the network is available. When this is enabled with "systemd enable NetworkManager-wait-online.service" the unit network.target will be delayed until the network is up, which is suitable for synchronizing NFS mounts and similar to it. https://bugzilla.redhat.com/show_bug.cgi?id=692008 2011-04-06 04:30:02 +02:00			`WantedBy=multi-user.target`
systemd: restore D-Bus service alias name Mistakenly removed while merging 86f14392fc94189d24c0e65dcc5b2db74ca709ae 2012-09-25 15:35:57 -05:00			`Alias=dbus-org.freedesktop.NetworkManager.service`
systemd: fix up dispatcher unit install (rh #948433) Lennart sez: "Oh, I wasn't aware it is short-lived only. In that case, drop the multi-user.target bit, and just make it create the dbus alias. [Install] Alias=dbus-org.freedesktop.nm-dispatcher.service And yeah, adding Also=NetworkManager-dispatcher.service to NetworkManager.service certainly would be a good idea." 2013-08-06 15:58:55 -05:00			`Also=NetworkManager-dispatcher.service`
systemd: also install nm-wait-online on 'systemctl enable' Inspired by openSUSE patches. There is no need to require user/distributor manually enable nm-wait-online. 2012-09-05 21:01:50 +02:00