systemd-stable/units/system-update.target

#  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=Offline System Update
Documentation=man:systemd.offline-updates(7)
Documentation=man:systemd.special(7) man:systemd-system-update-generator(8)
Requires=sysinit.target
After=sysinit.target system-update-pre.target
AllowIsolate=yes
Wants=system-update-cleanup.service
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			`#`
system-update: add system update generator http://freedesktop.org/wiki/Software/systemd/SystemUpdates 2012-05-22 19:48:51 +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]`
man: update the description of offline updates - use "service" instead of "script", because various offline updaters that we have aren't really scripts, e.g. dnf-plugin-system-upgrade, packagekit-offline-update, fwupd-offline-update. - strongly recommend After=sysinit.target, Wants=sysinit.target - clarify a bit what should happen when multiple update services are started - replace links to the wiki with refs to the man page that replaced it. 2016-11-29 01:19:24 -05:00			`Description=Offline System Update`
			`Documentation=man:systemd.offline-updates(7)`
man: document systemd-update-generator 2012-06-27 15:12:29 +02:00			`Documentation=man:systemd.special(7) man:systemd-system-update-generator(8)`
system-update: add system update generator http://freedesktop.org/wiki/Software/systemd/SystemUpdates 2012-05-22 19:48:51 +02:00			`Requires=sysinit.target`
units: fix typo in After= Followup for c7668c1ce04fa85370432d197d2ccd9411e85649. 2018-06-20 16:35:23 +02:00			`After=sysinit.target system-update-pre.target`
system-update: add system update generator http://freedesktop.org/wiki/Software/systemd/SystemUpdates 2012-05-22 19:48:51 +02:00			`AllowIsolate=yes`
units: add system-update-cleanup.service to guard against offline-update loops Note: the name is "system-update-cleanup.service" rather than "system-update-done.service", because it should not run normally, and also because there's already "systemd-update-done.service", and having them named so similarly would be confusing. In https://bugzilla.redhat.com/show_bug.cgi?id=1395686 the system repeatedly entered system-update.target on boot. Because of a packaging issue, the tool that created the /system-update symlink could be installed without the service unit that was supposed to perform the upgrade (and remove the symlink). In fact, if there are no units in system-update.target, and /system-update symlink is created, systemd always "hangs" in system-update.target. This is confusing for users, because there's no feedback what is happening, and fixing this requires starting an emergency shell somehow, and also knowing that the symlink must be removed. We should be more resilient in this case, and remove the symlink automatically ourselves, if there are no upgrade service to handle it. This adds a service which is started after system-update.target is reached and the symlink still exists. It nukes the symlink and reboots the machine. It should subsequently boot into the default default.target. This is a more general fix for https://bugzilla.redhat.com/show_bug.cgi?id=1395686 (the packaging issue was already fixed). 2016-11-29 01:29:02 -05:00			`Wants=system-update-cleanup.service`