systemd-timesyncd stores its clock file under /var/lib/systemd/timesync, so it can fail to save state if it starts before the volatile /var/lib is mounted. Add it to the Before= and WantedBy= entries already used for systemd-random-seed.service.
Signed-off-by: Esa Jaaskela <[email protected]> --- meta/recipes-core/volatile-binds/volatile-binds.bb | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/meta/recipes-core/volatile-binds/volatile-binds.bb b/meta/recipes-core/volatile-binds/volatile-binds.bb index 857bcc93ff..613e750c17 100644 --- a/meta/recipes-core/volatile-binds/volatile-binds.bb +++ b/meta/recipes-core/volatile-binds/volatile-binds.bb @@ -57,10 +57,11 @@ ${@d.getVar('VOLATILE_BINDS').replace("\\n", "\n")} END if [ -e "$var_lib_servicefile" ]; then - # As the seed is stored under /var/lib, ensure that this service runs - # after the volatile /var/lib is mounted. - sed -i -e "/^Before=/s/\$/ systemd-random-seed.service/" \ - -e "/^WantedBy=/s/\$/ systemd-random-seed.service/" \ + # The random seed and the timesyncd clock file are stored under + # /var/lib, so ensure that those services run after the volatile + # /var/lib is mounted. + sed -i -e "/^Before=/s/\$/ systemd-random-seed.service systemd-timesyncd.service/" \ + -e "/^WantedBy=/s/\$/ systemd-random-seed.service systemd-timesyncd.service/" \ "$var_lib_servicefile" fi } -- 2.47.3
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#242018): https://lists.openembedded.org/g/openembedded-core/message/242018 Mute This Topic: https://lists.openembedded.org/mt/120457028/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
