summaryrefslogtreecommitdiffstats
path: root/lib/oeqa/selftest
diff options
context:
space:
mode:
authorStefan Agner <stefan.agner@toradex.com>2020-06-15 08:27:36 +0000
committerPatrick Vacek <patrickvacek@gmail.com>2020-07-08 15:49:17 +0200
commit7951110d5be5ee5ff5a54173be5137e873527742 (patch)
tree3ef710d5924b3b2d1139a233ac73749fcc971d3c /lib/oeqa/selftest
parent6bdfa929bf43b3ec25e9926cadb54dd020032acc (diff)
downloadmeta-updater-7951110d5be5ee5ff5a54173be5137e873527742.tar.gz
aktualizr: make use of boot-complete.target
From the systemd.special(7) man page section boot-complete.target: This target is intended as generic synchronization point for services that shall determine or act on whether the boot process completed successfully. Let's make use of the target. Since aktualizr by default marks a boot as successful, we consider aktualizr.service a service which needs to be executed on successful boot (hence after the boot-complete.target). This allows to declare a service as crucial by simply ordering it before the boot-complete.target. The systemd example service systemd-boot-check-no-failures.service can serve as an example. This change does not add any service dependency by default as boot-complete.target by default does not has any extra dependencies. Note that rebooting in the failure case is not handled by this mechanism. This can be added by using FailureAction. Boot assessement infrastructure got introduced with systemd 240. See also: https://systemd.io/AUTOMATIC_BOOT_ASSESSMENT/ Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
Diffstat (limited to 'lib/oeqa/selftest')
0 files changed, 0 insertions, 0 deletions