units/systemd-rfkill.service.in

#  SPDX-License-Identifier: LGPL-2.1-or-later
#
#  This file is part of systemd.
#
#  systemd is free software; you can redistribute it and/or modify it
#  under the terms of the GNU Lesser General Public License as published by
#  the Free Software Foundation; either version 2.1 of the License, or
#  (at your option) any later version.

[Unit]
Description=Load/Save RF Kill Switch Status
Documentation=man:systemd-rfkill.service(8)
ConditionPathExists=!/etc/initrd-release

DefaultDependencies=no
BindsTo=sys-devices-virtual-misc-rfkill.device
Conflicts=shutdown.target
After=sys-devices-virtual-misc-rfkill.device
Before=shutdown.target

[Service]
ExecStart={{LIBEXECDIR}}/systemd-rfkill
NoNewPrivileges=yes
StateDirectory=systemd/rfkill
TimeoutSec=90s
Type=notify
license: LGPL-2.1+ -> LGPL-2.1-or-later 2020-11-09 13:23:58 +09:00			`# SPDX-License-Identifier: LGPL-2.1-or-later`
Add SPDX license headers to unit files 2017-11-18 17:35:03 +01:00			`#`
rfkill: add new rfkill tool to save/restore rfkill state across reboots This works analogous to the existing backlight and random seed services 2013-10-14 04:31:49 +02:00			`# This file is part of systemd.`
			`#`
			`# systemd is free software; you can redistribute it and/or modify it`
			`# under the terms of the GNU Lesser General Public License as published by`
			`# the Free Software Foundation; either version 2.1 of the License, or`
			`# (at your option) any later version.`

			`[Unit]`
rfkill: rework and make it listen on /dev/rfkill With this rework we introduce systemd-rfkill.service as singleton that is activated via systemd-rfkill.socket that listens on /dev/rfkill. That way, we get notified each time a new rfkill device shows up or changes state, in which case we restore and save its current setting to disk. This is nicer than the previous logic, as this means we save/restore state even of rfkill devices that are around only intermittently, and save/restore the state even if the system is shutdown abruptly instead of cleanly. This implements what I suggested in #1019 and obsoletes it. 2015-10-01 14:32:48 +02:00			`Description=Load/Save RF Kill Switch Status`
			`Documentation=man:systemd-rfkill.service(8)`
units: condition out a few services in the initrd Let's make our units more robust to being added to an initrd: 1. systemd-boot-update only makes sense if sd-boot is available in /usr/ to copy into the ESP. This is generally not the case in initrds, and even if it was, we shouldn't update the ESP from the initrd, but from the host instead. 2. The rfkill services save/restore rfkill state, but that information is only available once /var/ is mounted, which generally happens after the initrd transition. 3. utmp management is partly in /var/, and legacy anyway, hence don't bother with it in the initrd. 2023-07-04 22:31:11 +02:00			`ConditionPathExists=!/etc/initrd-release`

rfkill: add new rfkill tool to save/restore rfkill state across reboots This works analogous to the existing backlight and random seed services 2013-10-14 04:31:49 +02:00			`DefaultDependencies=no`
rfkill: rework and make it listen on /dev/rfkill With this rework we introduce systemd-rfkill.service as singleton that is activated via systemd-rfkill.socket that listens on /dev/rfkill. That way, we get notified each time a new rfkill device shows up or changes state, in which case we restore and save its current setting to disk. This is nicer than the previous logic, as this means we save/restore state even of rfkill devices that are around only intermittently, and save/restore the state even if the system is shutdown abruptly instead of cleanly. This implements what I suggested in #1019 and obsoletes it. 2015-10-01 14:32:48 +02:00			`BindsTo=sys-devices-virtual-misc-rfkill.device`
Revert "units: Add missing dependencies on initrd-switch-root.target" This reverts commit f0ad3e6b9652fe785245934ff8604cc897d3b8f4. 2023-05-15 13:52:41 +02:00			`Conflicts=shutdown.target`
units: drop systemd-remount-fs.service dependency from more services All services using StateDirectory= don't need the explicit dep anymore, let's hence drop it everywhere. 2020-04-08 16:24:23 +02:00			`After=sys-devices-virtual-misc-rfkill.device`
Revert "units: Add missing dependencies on initrd-switch-root.target" This reverts commit f0ad3e6b9652fe785245934ff8604cc897d3b8f4. 2023-05-15 13:52:41 +02:00			`Before=shutdown.target`
rfkill: add new rfkill tool to save/restore rfkill state across reboots This works analogous to the existing backlight and random seed services 2013-10-14 04:31:49 +02:00
			`[Service]`
Drop split-usr and unmerged-usr support As previously announced, execute order 66: https://lists.freedesktop.org/archives/systemd-devel/2022-September/048352.html The meson options split-usr, rootlibdir and rootprefix become no-ops that print a warning if they are set to anything other than the default values. We can remove them in a future release. 2023-06-12 02:15:19 +01:00			`ExecStart={{LIBEXECDIR}}/systemd-rfkill`
units: set NoNewPrivileges= for all long-running services Previously, setting this option by default was problematic due to SELinux (as this would also prohibit the transition from PID1's label to the service's label). However, this restriction has since been lifted, hence let's start making use of this universally in our services. On SELinux system this change should be synchronized with a policy update that ensures that NNP-ful transitions from init_t to service labels is permitted. An while we are at it: sort the settings in the unit files this touches. This might increase the size of the change in this case, but hopefully should result in stabler patches later on. Fixes: #1219 2018-11-12 17:19:48 +01:00			`NoNewPrivileges=yes`
unit: use StateDirectory= instead of RequiresMountsFor= 2017-08-31 18:37:11 +09:00			`StateDirectory=systemd/rfkill`
units: Bump various oneshot unit timeouts to 90s In mkosi, we've been having CI failures caused by systemd-machine-id-commit.service timing out. Let's bump the timeout for it and systemd-rfkill.service to 90s which we also use for other oneshot services to avoid transient failures on slower systems. 2024-03-13 10:26:52 +01:00			`TimeoutSec=90s`
units: set NoNewPrivileges= for all long-running services Previously, setting this option by default was problematic due to SELinux (as this would also prohibit the transition from PID1's label to the service's label). However, this restriction has since been lifted, hence let's start making use of this universally in our services. On SELinux system this change should be synchronized with a policy update that ensures that NNP-ful transitions from init_t to service labels is permitted. An while we are at it: sort the settings in the unit files this touches. This might increase the size of the change in this case, but hopefully should result in stabler patches later on. Fixes: #1219 2018-11-12 17:19:48 +01:00			`Type=notify`