From: pdmorrow@gmail.com
To: openembedded-devel@lists.openembedded.org
Cc: Peter Morrow <peter.morrow@microsoft.com>
Subject: [meta-networking][PATCH] chrony: install chrony-wait.service
Date: Tue, 19 Nov 2019 15:45:39 +0000 [thread overview]
Message-ID: <20191119154539.22200-1-pdmorrow@gmail.com> (raw)
From: Peter Morrow <peter.morrow@microsoft.com>
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 <peter.morrow@microsoft.com>
---
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
next reply other threads:[~2019-11-19 15:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-19 15:45 pdmorrow [this message]
2019-11-20 14:39 ` [meta-networking][PATCH] chrony: install chrony-wait.service Khem Raj
2019-11-20 16:03 ` Peter Morrow
2019-11-20 16:11 ` Khem Raj
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191119154539.22200-1-pdmorrow@gmail.com \
--to=pdmorrow@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=peter.morrow@microsoft.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.