Kernel/iwd
3
0
Fork 0
mirror of https://git.kernel.org/pub/scm/network/wireless/iwd.git synced 2024-12-19 10:02:33 +01:00
Code Releases Activity
c352b35bf1
iwd/wired/ead.service.in

29 lines
551 B
SYSTEMD
Raw Normal View History

build: Add systemd service configuration for Ethernet daemon
2018-09-14 14:09:53 +02:00
[Unit]
Description=Ethernet service
build: Add documention of manual pages to systemd service file
2022-11-18 10:20:28 +01:00
Documentation=man:ead(8)
build: add After=network-pre.target to service files systemd specifies a special passive target unit 'network-pre.target' which may be pulled in by services that want to run before any network interface is brought up or configured. Correspondingly, network management services such as iwd and ead should specify After=network-pre.target to ensure a proper ordering with respect to this special target. For more information on network-pre.target, see systemd.special(7). Two examples to explain the rationale of this change: 1. On one of our embedded systems running iwd, a oneshot service is run on startup to configure - among other things - the MAC address of the wireless network interface based on some data in an EEPROM. Following the systemd documentation, the oneshot service specifies: Before=network-pre.target Wants=network-pre.target ... to ensure that it is run before any network management software starts. In practice, before this change, iwd was starting up and connecting to an AP before the service had finished. iwd would then get kicked off by the AP when the MAC address got changed. By specifying After=network-pre.target, systemd will take care to avoid this situation. 2. An administrator may wish to use network-pre.target to ensure firewall rules are applied before any network management software is started. This use-case is described in the systemd documentation[1]. Since iwd can be used for IP configuration, it should also respect the After=network-pre.target convention. Note that network-pre.target is a passive unit that is only pulled in if another unit specifies e.g. Wants=network-pre.target. If no such unit exists, this change will have no effect on the order in which systemd starts iwd or ead. [1] https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/
2021-01-22 15:41:23 +01:00
After=network-pre.target
build: Add systemd service configuration for Ethernet daemon
2018-09-14 14:09:53 +02:00
Before=network.target
Wants=network.target
[Service]
Type=dbus
BusName=net.connman.ead
ExecStart=@libexecdir@/ead
build: Use NotifyAccess=main feature when running under systemd
2019-09-08 20:36:57 +02:00
NotifyAccess=main
build: Add systemd service configuration for Ethernet daemon
2018-09-14 14:09:53 +02:00
LimitNPROC=1
build: Fix issue with incorrect ReadWritePaths in unit files
2019-08-03 09:52:28 +02:00
Restart=on-failure
build: Start using CapabilityBoundingSet option from systemd
2019-09-08 20:26:49 +02:00
CapabilityBoundingSet=CAP_NET_ADMIN CAP_NET_RAW
build: Fix issue with incorrect ReadWritePaths in unit files
2019-08-03 09:52:28 +02:00
PrivateTmp=true
NoNewPrivileges=true
PrivateDevices=true
ProtectHome=yes
ProtectSystem=strict
ProtectControlGroups=yes
ProtectKernelModules=yes
build: Add ConfigurationDirectory= option to service files
2019-09-08 10:25:39 +02:00
ConfigurationDirectory=ead
build: Add StateDirectory= option to service files
2019-09-08 19:56:21 +02:00
StateDirectory=ead
build: Add StateDirectoryMode=0700 option to systemd service
2019-09-09 06:55:22 +02:00
StateDirectoryMode=0700
build: Add systemd service configuration for Ethernet daemon
2018-09-14 14:09:53 +02:00
[Install]
WantedBy=multi-user.target
Copy Permalink