diff options
| author | Wes Lindauer <wesley.lindauer@gmail.com> | 2021-04-11 23:50:34 -0400 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2021-04-20 13:56:48 +0100 |
| commit | ada30f109150761aa1c9bb55c5a5d554c4cb9590 (patch) | |
| tree | 15c5390e1bd73169c64c37ac83a0eb8c3a2585b6 /meta/recipes-core | |
| parent | d08d362cf98e9f3b6e99f4f9e33638e1fceffbaf (diff) | |
| download | poky-ada30f109150761aa1c9bb55c5a5d554c4cb9590.tar.gz | |
oeqa/runtime/cases: Only disable/enable for current boot
Previously doing a stop/start worked, but using a disable/enable does
not work on a read-only rootfs. Add a --runtime flag to systemctl so
that systemd only modifies the current boot and does not attempt to
write to the filesystem.
This also keeps the test from making a permanent (one could argue
policy) change to the running system being tested. i.e. What if the
image being tested had intentionally disabled the timesyncd service in
preference to using chrony or ntpd? The test shouldn't assume that the
user wants the timesyncd service enabled.
(From OE-Core rev: 43dd83b6a325589368c980a3f17cab90935aaeb0)
Signed-off-by: Wes Lindauer <wesley.lindauer@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-core')
0 files changed, 0 insertions, 0 deletions