| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
| |
|
|
| |
Signed-off-by: Mykhaylo Sul <ext-mykhaylo.sul@here.com>
|
| |
|
|
|
|
|
| |
aktualizr.service needs run after nss-lookup.target to ensure DNS
resolving is ready.
Signed-off-by: Ming Liu <liu.ming50@gmail.com>
|
| |
|
|
|
|
|
| |
This should make the secondary config dir process better anyway, and it
finally gets rid of a hacky workaround that we'd been using for ages.
Signed-off-by: Patrick Vacek <patrickvacek@gmail.com>
|
| | |
|
| |
|
|
|
|
| |
Includes the suggestion for using /etc/sota/sota.env if it exists as
recommended by the discussion here:
https://github.com/advancedtelematic/meta-updater/pull/275
|
| | |
|
|
|
We don't support this scenario any more and it makes testing more complicated.
|
