On Fri, Jul 12, 2024 at 2:32 PM Jan Claußen <jan.clausse...@web.de> wrote: > > Hi, > > I have some questions about chrony. I am trying to set up chrony as local NTP > server. First I tried to completely substitute systemd-timesyncd with chrony, > but this turned out as quite the challenge, because at least on a Yocto > system some services are dependent on systemd's timesyncd module. > > So to not make me suffer more than necessary figuring out how to make all > these other services happy, I would like to ise chrony only as an NTP server > for some other client devices, which are not directly connected to the > internet. This would require me to run timesyncd and chronyd at the same > time. So I would have some questions: > > Is it problematic to run chrony alongside timesyncd, even when only used as a > server?
systemd-timesyncd implements SNTP, it periodically updates system time. chronyd will perceive it as erratic time jumps which will probably result in rather bad quality for external clients. > How would I accomplish this? Online it says to use the local directive. I am > not entirely sure if chrony syncs with the hardware clock here. Since RTCs > are said to drift quite a lot, I would rather have chrony sync itself with > the system clock My understanding is that chronyd will simply get whatever system time there is. > If the hardware clock indeed does sync from the RTC, what is the refclock > directive needed for? Can I actually use the RTC here is this for another > purpose? I am not sure what you call a "hardware clock" here. For me RTC *is* hardware clock. -- To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org with "unsubscribe" in the subject. For help email chrony-users-requ...@chrony.tuxfamily.org with "help" in the subject. Trouble? Email listmas...@chrony.tuxfamily.org.
