| 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: Laurent Bonnans <laurent.bonnans@here.com>
|
| |
|
|
|
|
|
| |
This allows you to see how much bandwidth was used with `systemd status
aktualizr`.
Signed-off-by: Patrick Vacek <patrickvacek@gmail.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>
|
| |
|
|
|
|
| |
to start Seconadry daemon
Signed-off-by: Mike Sul <ext-mykhaylo.sul@here.com>
|
| |
|
|
| |
Signed-off-by: Laurent Bonnans <laurent.bonnans@here.com>
|
| |
|
|
|
|
| |
For controlling systemd cgroups configuration of the aktualizr daemon
Signed-off-by: Laurent Bonnans <laurent.bonnans@here.com>
|
| |
|
|
| |
Signed-off-by: Laurent Bonnans <laurent.bonnans@here.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
|
| | |
|
| |
|
|
| |
Also, timeout communication to the DUT after 60s.
|
| | |
|
| | |
|
| | |
|
| |\
| |
| | |
Provide user interface to add legacy secondary bridge
|
| | | |
|
| |/
|
|
| |
This enables backwards incompatible changes to configuration format
|
| |
|
|
| |
We don't support this scenario any more and it makes testing more complicated.
|
| | |
|
| | |
|
| |
|
|
| |
It should be able to be updated.
|
| |
|
|
|
|
|
|
| |
Split aktualizr into basic and native recipes by moving most of the work
to an include file. Use aktualizr-implicit-writer (on host) to do the
actual work of configuring sota.toml and installing files.
Still not quite fully functional.
|
| |\
| |
| | |
Remove useless/obsolete --disable-keyid-validation option.
|
| | | |
|
| |/
|
|
|
|
|
| |
Provide Aktualizr systemd service and configurations
for manual and autoprovision in a separate recipe.
Signed-off-by: Leon Anavi <leon.anavi@konsulko.com>
|
| | |
|
| |
|
|
|
| |
Warn if older credential environment variables are set. They are now
ignored since the credentials aren't unpacked during building.
|
| |
|
|
|
| |
Perform sync() after provisioning
Store sota.toml in updatable /usr directory
|
| | |
|
|
|
Aktualizr currently supports OSTree updates in non-autoprovisioned mode. Add a
systemd service to run it in that mode. It uses the same location for the
config file as rvi-sota-client (/sysroot/boot/sota.toml)
Also, the aktualizr recipe is reformatted according to
meta-openembedded/contrib/oe-stylize.py (which follows the OE styleguide)
|
