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

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

40 lines
1.4 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@
systemd: add "BindsTo=dbus.service" to NetworkManager.service Add "BindsTo=dbus.service" to NetworkManager.service so that when the D-Bus service gets restarted, NM is also restarted instead of staying stopped. https://bugzilla.redhat.com/show_bug.cgi?id=2161915 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/1605
2023-04-13 15:50:15 +02:00
BindsTo=dbus.service
core: add systemd unit support
2010-08-12 11:15:26 -05:00
[Service]
Type=dbus
BusName=org.freedesktop.NetworkManager
systemd: use busctl instead of dbus-send While dbus-send may not be installed, busctl is shipped with systemd and so it should be always available.
2019-09-09 16:59:02 +02:00
ExecReload=/usr/bin/busctl call org.freedesktop.NetworkManager /org/freedesktop/NetworkManager org.freedesktop.NetworkManager Reload u 0
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=/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
Revert "service: don't give CAP_DAC_OVERRIDE capability to NetworkManager" Well, that was short. Seems we need CAP_DAC_OVERRIDE at least for the OVS plugin. The OVS socket is srwxr-x---. 1 openvswitch openvswitch 0 Xxx xx xx:xx /run/openvswitch/db.sock and without CAP_DAC_OVERRIDE, NetworkManager cannot talk to OVS. We should fix that differently by adding a nm-sudo D-Bus service that can hand a file descriptor to NetworkManager. This reverts commit 2e334f54b27f91f40c3aa8bdba3254e2284d30bd.
2021-02-12 13:06:13 +01:00
service: increase start timeout of NetworkManager.service With a large number of interfaces, it can take longer than 45 seconds before NetworkManager is started (and the D-Bus name acquired). Increase the start timeout. https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/1612
2023-04-21 19:49:18 +02:00
# With a huge number of interfaces, starting can take a long time.
TimeoutStartSec=600
service: add CAP_BPF capability to NetworkManager Since we are now always building n-acd with eBPF, and are able to detect eBPF support at runtime, we can reflect this in the unit as well. Add CAP_BPF to CapabilityBoundingSet, so that NM can request to create a BPF map when setting up n-acd.
2025-10-20 10:49:27 +02:00
CapabilityBoundingSet=CAP_NET_ADMIN CAP_DAC_OVERRIDE CAP_NET_RAW CAP_BPF 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
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
core: increase limit of open file descriptors for NetworkManager.service Note that POSIX select() can only handle up to 1024 descriptors. That means, our code (and the libraries that we use) must not use select(). Note that libndp uses select(), which means NetworkManager will crash when using file descriptors larger than 1023. On the other hand, depriving NetworkManager of file descriptors will also crash it. So libndp must be fixed ([1]). [1] https://listman.redhat.com/archives/libndp-list/2021-February/msg00000.html https://bugzilla.redhat.com/show_bug.cgi?id=1926599
2021-02-28 11:18:16 +01:00
# We require file descriptors for DHCP etc. When activating many interfaces,
# the default limit of 1024 is easily reached.
LimitNOFILE=65536
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: 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
systemd: make enablement of n-m-wait-online.service follow n-m.service This is the approach used by systemd-networkd. I don't understand the logic that caused systemd-networkd to make the change - https://github.com/systemd/systemd/commit/9e49656037717b96c06b1f1507a41550bdb2c795 Instead, I am suggesting it for consistency, and because it seems to me this is the exact correct behaviour. Because if you enable NetworkManager, and rely on it to configure your network devices, then network mounts will not start correctly at boot time unless you also enable NetworkManager-wait-online.service. Enabling NetworkManager-wait-online.service does not cause unnecessary serialization of the boot process; it is only pulled in if something else (like a network mount) pulls in network-online.target. I am suggesting this in response to reading this user support request [1]. [1] https://unix.stackexchange.com/questions/429604/fstab-not-automatically-mounting-smb-storage [thaller@redhat.com: reworded commit message] https://github.com/NetworkManager/NetworkManager/pull/76
2018-03-11 21:48:46 +00:00
# We want to enable NetworkManager-wait-online.service whenever this service
# is enabled. NetworkManager-wait-online.service has
# WantedBy=network-online.target, so enabling it only has an effect if
# network-online.target itself is enabled or pulled in by some other unit.
Also=NetworkManager-wait-online.service
Reference in a new issue Copy permalink