Hoi Miroslav,
and thanks for the input! A systemd ExecStartPre in chronyd.service that does this via e.g. core-utils:hwclock is a/the workaround... The proposed opt-in feature (as it is off by default) could IMO still be a good fit for chrony, when it is used on (embedded) systems as the sole keeper of the RTC. Thoughts? gruß Johannes ________________________________________ From: Miroslav Lichvar <mlich...@redhat.com> Sent: Monday, July 1, 2024 10:07 To: SCHNEIDER Johannes Cc: chrony-dev@chrony.tuxfamily.org Subject: Re: [chrony-dev] [PATCH v1] rtc: handle uninitialized RTC [You don't often get email from mlich...@redhat.com. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ] This email is not from Hexagon’s Office 365 instance. Please be careful while clicking links, opening attachments, or replying to this email. On Mon, Jul 01, 2024 at 07:50:09AM +0000, SCHNEIDER Johannes wrote: > no there wasn't a kernel side discussion; > On a system where chrony is running it holds the rtc device/file-handle, e.g. > has exclusive access and manages the RTC -> there are no other applications > reading/handling the RTC. > So this patch adds the missing "userspace handling" for this uninitialized > RTC corner case. There are other applications supporting RTCs, which other users might be using, and they would eventually need to handle this corner case too, right? To me it seems it's better to handle this in the place that already has HW-specific code, the driver. If the RTC maintainers reject that for some reason, then maybe a simple script running on boot using hwclock. -- Miroslav Lichvar -- To unsubscribe email chrony-dev-requ...@chrony.tuxfamily.org with "unsubscribe" in the subject. For help email chrony-dev-requ...@chrony.tuxfamily.org with "help" in the subject. Trouble? Email listmas...@chrony.tuxfamily.org.
