mirror of
https://github.com/systemd/systemd
synced 2024-09-06 16:56:43 +00:00
49c55abcbe
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.
27 lines
860 B
SYSTEMD
27 lines
860 B
SYSTEMD
# 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=Record System Boot/Shutdown in UTMP
|
|
Documentation=man:systemd-update-utmp.service(8) man:utmp(5)
|
|
ConditionPathExists=!/etc/initrd-release
|
|
|
|
DefaultDependencies=no
|
|
After=systemd-remount-fs.service systemd-tmpfiles-setup.service auditd.service
|
|
Before=sysinit.target
|
|
Conflicts=shutdown.target
|
|
Before=shutdown.target
|
|
RequiresMountsFor=/var/log/wtmp
|
|
|
|
[Service]
|
|
Type=oneshot
|
|
RemainAfterExit=yes
|
|
ExecStart={{ROOTLIBEXECDIR}}/systemd-update-utmp reboot
|
|
ExecStop={{ROOTLIBEXECDIR}}/systemd-update-utmp shutdown
|