From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: TIAN Yuanhao <tianyuanhao3@163.com>
Cc: buildroot@buildroot.org, Bernd Kuhls <bernd@kuhls.net>,
Fabrice Fontaine <fontaine.fabrice@gmail.com>,
Scott Fan <fancp2007@gmail.com>,
"Yann E. MORIN" <yann.morin@orange.com>
Subject: Re: [Buildroot] [PATCH 1/1] package/chrony: switch chrony.service to Type=notify
Date: Sat, 3 Oct 2026 20:40:31 +0200 [thread overview]
Message-ID: <asFMGgD1V4TYbifi@windsurf> (raw)
In-Reply-To: <20260904134208.4707-1-tianyuanhao3@163.com>
On Fri, Sep 04, 2026 at 06:42:08AM -0700, TIAN Yuanhao wrote:
> Since 4.7, chronyd implements the systemd notify protocol natively
> (upstream commit cb11184, "main: add support for systemd
> notification"): it sends READY=1 to $NOTIFY_SOCKET once fully
> initialised and ready to accept commands.
>
> Type=simple cannot observe that signal. systemd marks the unit active
> as soon as the process starts, before chronyd is ready, and gpsd may
> follow immediately: its drop-in br-chrony.conf orders it only with
> After=chrony.service.
>
> Switch to Type=notify so the ordering holds. chronyd's -n mode
> (don't detach) suits Type=notify, and no libsystemd dependency
> is added.
>
> Cc: Bernd Kuhls <bernd@kuhls.net>
> Cc: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> Cc: Scott Fan <fancp2007@gmail.com>
> Cc: Yann E. MORIN <yann.morin@orange.com>
> Signed-off-by: TIAN Yuanhao <tianyuanhao3@163.com>
Applied to master, thanks!
Best regards,
Thomas Petazzoni
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2026-10-03 18:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-04 13:42 [Buildroot] [PATCH 1/1] package/chrony: switch chrony.service to Type=notify TIAN Yuanhao
2026-10-03 18:40 ` Thomas Petazzoni via buildroot [this message]
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=asFMGgD1V4TYbifi@windsurf \
--to=buildroot@buildroot.org \
--cc=bernd@kuhls.net \
--cc=fancp2007@gmail.com \
--cc=fontaine.fabrice@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=tianyuanhao3@163.com \
--cc=yann.morin@orange.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox