Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | units: make system-update-pre.target a passive unit (#9349) | Lennart Poettering | 2018-06-20 | 1 | -1/+0 |
| | | | | | | | This is an additional synchronization point normally not needed. Hence, let's make it passive, i.e. pull it in from the unit which wants to be ordered before the update service rather than by the update service itself. | ||||
* | units: Add new system-update-pre.target | Hans de Goede | 2018-06-19 | 1 | -0/+16 |
systemd offline-updates allows dropping multiple system update units to be added to system-update.target.wants. As documented in systemd.offline-updates(7) only 1 of these units should actually be active (based on the /system-update symlink) and when that unit is done it should reboot the system. In some cases it is desirable to run a unit whenever booting in offline-updates mode indepedent of which update unit is going to handle the update. One example of this is integration with bootloader code which checks if the previous boot was succesful. Since the active unit will reboot the system when it is done, there is no guarantee that adding such a unit to system-update.target.wants will get it executed always. This commit adds a system-update-pre.target which can be used for units which should always run when booting in offline-updates mode. |