fdo-mirrors/NetworkManager
1
0
Fork 0
mirror of https://gitlab.freedesktop.org/NetworkManager/NetworkManager.git synced 2025-12-20 15:10:05 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions
NetworkManager/data/NetworkManager.service.in

30 lines
1 KiB
SYSTEMD
Raw Normal View History

core: add systemd unit support
2010-08-12 11:15:26 -05:00
[Unit]
Description=Network Manager
systemd: add Documentation to service files Reference the nm-online and NetworkManager man page in the corresponding service files. https://www.freedesktop.org/software/systemd/man/systemd.unit.html#Documentation= https://bugzilla.gnome.org/show_bug.cgi?id=767168
2016-06-02 17:41:29 +02:00
Documentation=man:NetworkManager(8)
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
systemd: order NetworkManager.serivce after network-pre.target https://bugzilla.gnome.org/show_bug.cgi?id=761001
2016-01-23 16:54:33 +01:00
After=network-pre.target dbus.service
systemd: add "Before=network.service" on Fedora/RHEL (rh #1034983) On Fedora/RHEL, NetworkManager.service needs to be started before network.service, or else network.service may try to bring up NM's devices itself.
2013-12-16 14:42:40 -05:00
Before=network.target @DISTRO_NETWORK_SERVICE@
core: add systemd unit support
2010-08-12 11:15:26 -05:00
[Service]
Type=dbus
BusName=org.freedesktop.NetworkManager
systemd: update service unit file to use dbus-send for ExecReload instead of `kill -HUP`. We support "org.freedesktop.NetworkManager.Reload" D-Bus method for a long time now. Use it because it is synchronous.
2017-06-07 10:47:40 +02:00
ExecReload=/usr/bin/dbus-send --print-reply --system --type=method_call --dest=org.freedesktop.NetworkManager /org/freedesktop/NetworkManager org.freedesktop.NetworkManager.Reload uint32:0
#ExecReload=/bin/kill -HUP $MAINPID
core: add systemd unit support
2010-08-12 11:15:26 -05:00
ExecStart=@sbindir@/NetworkManager --no-daemon
core: tell systemd to restart NetworkManager.service if it exited with failure (bgo #741587) Crashed NetworkManager.service was not restarted by systemd. Signed-off-by: Mikko Rapeli <mikko.rapeli@iki.fi> https://bugzilla.gnome.org/show_bug.cgi?id=741587
2014-12-15 16:47:45 +01:00
Restart=on-failure
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
systemd: add chroot capability CAP_SYS_CHROOT is needed for openvpn hardening.
2016-01-22 22:11:07 +01:00
CapabilityBoundingSet=CAP_NET_ADMIN CAP_DAC_OVERRIDE CAP_NET_RAW CAP_NET_BIND_SERVICE CAP_SETGID CAP_SETUID CAP_SYS_MODULE CAP_AUDIT_WRITE CAP_KILL CAP_SYS_CHROOT
doc: add comment to systemd's NetworkManager.service about ibft requiring CAP_SYS_ADMIN We don't want to enable this upstream, but make the requirement more discoverable by documenting it and put a comment to NetworkManager.service. https://bugzilla.redhat.com/show_bug.cgi?id=1371201
2016-09-02 13:35:00 +02:00
# ibft settings plugin calls iscsiadm which needs CAP_SYS_ADMIN
#CapabilityBoundingSet=CAP_SYS_ADMIN
service: harden the NetworkManager service a bit Tested with dnsmasq (ipv4.method=shared), openvpn & vpnc. https://bugzilla.gnome.org/show_bug.cgi?id=750598
2015-06-04 14:30:02 +02:00
ProtectSystem=true
ProtectHome=read-only
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
Reference in a new issue Copy permalink