From: Peter Morrow <[email protected]> Any systemd service which needs to wait on ntp synchronization before starting can order themselves after chrony-wait.service. It's useful to install this service as part of the recipe as it saves needing to install it via a bbappend file. Note that even if the service is installed no start up delay is introduced unless another service orders itself after the systemd target time-sync.target.
Signed-off-by: Peter Morrow <[email protected]> --- meta-networking/recipes-support/chrony/chrony_3.5.bb | 3 +++ 1 file changed, 3 insertions(+) diff --git a/meta-networking/recipes-support/chrony/chrony_3.5.bb b/meta-networking/recipes-support/chrony/chrony_3.5.bb index 7c6356d26..fa11c443e 100644 --- a/meta-networking/recipes-support/chrony/chrony_3.5.bb +++ b/meta-networking/recipes-support/chrony/chrony_3.5.bb @@ -103,6 +103,9 @@ do_install() { install -d ${D}${systemd_unitdir}/system install -m 0644 ${S}/examples/chronyd.service ${D}${systemd_unitdir}/system/ + # systemd chronyd synchronization unit configuration file + install -m 0644 ${S}/examples/chrony-wait.service ${D}${systemd_unitdir}/system/ + # Variable data (for drift and/or rtc file) install -d ${D}${localstatedir}/lib/chrony -- 2.20.1 -- _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-devel
