Re: Chrony and systemd-timesyncd

Jan Claußen <jan.claussen10-S0/[email protected]> Wed, 17 Jul 2024 12:08:26 +0200
Newsgroups gmane.comp.time.chrony.user
Message-ID <[email protected]>
> With rtcdrift you will need to add also
> rtcautotrim to the config or periodically call chronyc trimrtc.
Both of these don't work unfortunately. chronc reports me 513 RTC driver not running, although I have everything set.

I am btw missing an /etc/adjtime file, since our rootfs including /etc is read-only. Could that be a problem?
On Juli 17 2024, at 9:49 am, Miroslav Lichvar <[email protected]> wrote:
> On Tue, Jul 16, 2024 at 03:42:05PM +0200, Jan Claußen wrote:
> > So I found online that an rtcfile directive is needed for the rtcdata command to work. I am still getting the above error message now. Makes me wonder if RTC syncing ever worked with the rtcsync directive present. There was never really a log about chrony syncing to the RTC. I have now tried to manually set the RTC to a wrong value and have waited more than 11 minutes. The RTC is still not getting set.
>
> Are you trying that with rtcsync or rtcdrift?
> With rtcsync there are no log messages from chronyd. It's the kernel's
> job to sync the RTC. With rtcdrift you will need to add also
> rtcautotrim to the config or periodically call chronyc trimrtc.
>
> https://chrony-project.org/faq.html#_what_is_the_real_time_clock_rtc
> --
> Miroslav Lichvar
>
>
> --
> To unsubscribe email [email protected]
> with "unsubscribe" in the subject.
> For help email [email protected]
> with "help" in the subject.
> Trouble? Email [email protected].
>