| Re: [chrony-users] Requesting some insight regarding preferred servers and RTCSYNC/RTCFILE |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
On Mon, Oct 29, 2018 at 10:04:02AM +0000, Martin Janse wrote:
> My first concern lies with the RTC. In the current configuration, neither RTCSYNC nor RTCFILE are defined. Does Chrony still correct the system time while it's running? Or only at boot? Or never?
If no rtcfile or rtcsync is in the config, chronyd will not care about
the RTC at all. It will not track its frequency offset relative to the
system time, and correct for drift with the -s option, or tell the
kernel to synchronize it. If the RTC drifts, the initial time on start
will be wrong.
I guess that's what you want as you seem to synchronize the system
clock to (the same?) RTC using a SOCK refclock.
> Secondly, a new feature needs to be added to the system. Other than syncing to the RTC or other devices on the network, an NTP server needs to be added that has precedence over any other source. I saw in the manual that the parameter 'prefer' can be added to the server, causing Chrony to prefer that server. However, is there a scenario where Chrony still picks a non-preferred source? Is there a degree of 'quality' that the preferred server needs to have in order to have guaranteed precedence?
chronyd can select a non-prefered source if it doesn't agree with
other sources (falseticker). If you had only two sources, an RTC and
an NTP server, it would be easy for them to not agree and chronyd
would stop synchronization.
To always select the source, it needs to be specified with the "trust"
option.
--
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.