| Re: [chrony-users] Chrony and systemd-timesyncd |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: chrony-users@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-users] Chrony and systemd-timesyncd
- From: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
- Date: Wed, 17 Jul 2024 12:37:07 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1721212634; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=5qhmV//VdbWjyVTarNMPFxYyK2UCokHxl5uoA1tyY24=; b=EfK83KpfOfSLDyJ08STO9pgvMPVOi+9BaB+LRUPqtFWL6jLssz4lydFUr5h8fSPfkJE2ih jt2BpAaPIn/tPzUNbKIikwj03YDDCjxn/ikTDB860a+MB3gXoz+nCkk2etToxlO4tiAbBN O7uBrHnGsBYo6rOd+t9yx8ihyT5pj+M=
On Wed, Jul 17, 2024 at 12:08:26PM +0200, Jan Claußen wrote:
> > 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?
No, that could cause only a local/UTC mismatch.
What RTC driver is your machine using? Maybe it doesn't support
interrupts.
--
Miroslav Lichvar
--
To unsubscribe email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "unsubscribe" in the subject.
For help email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.