3 Commits

Author	SHA1	Message	Date
Zbigniew Jędrzejewski-Szmek	a7df2d1e43	Add SPDX license headers to unit files	2017-11-19 19:08:15 +01:00
Alan Jenkins	0b9ad5bf2e	units: add missing Before=shutdown.target for units which it Conflicts ... There's a few services missing this ordering. Also remove a duplicate Conflicts=shutdown.target from systemd-volatile-root.service.	2017-09-30 22:01:42 +01:00
Zbigniew Jędrzejewski-Szmek	953bf4604f	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:40:34 -05:00