> Why do application require a specific time synchronisation tool?! It is not obvious to me either. Neither systemd nor ntpd are listed as dependencies. One of the packages failing to build is net-snmp. Might be related to system time somehow. systemd is deeply interwoven with the system. The timedatectl timesync-status command will start timesyncd which conflicts with chrony. It is just hard to get rid of it, although probably not impossible.
> Well, if you cannot change them, maybe you can configure timesyncd to > synchronise to localhost? What do you mean by synchronize to localhost? Unfortunately you can't configure timesyncd as thoroughly as chrony. Have not found an option to have it not set the RTC or whatever. It is pretty much automated. On Juli 12 2024, at 2:23 pm, Jan Claußen <jan.clausse...@web.de> wrote: > > 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. > > What do you mean by bad quality? I know chrony is supposed to be more > correct, but I think the SNTP quality would be enough for my needs. As long > as there are no major issues, this would be fine for me. > > I am not sure what you call a "hardware clock" here. For me RTC *is* > > hardware clock. > From my understanding the hardware clock is the RTC as opposed to the system > clock which is manged by the kernel in software. > > > My understanding is that chronyd will simply get whatever system time there > > is. > This is why I am asking whether it is the hardware clock or system clock. > Would be nice if this could be specified the config. It is probably possible > > On Juli 12 2024, at 2:06 pm, MUZZULINI Frank <frank.muzzul...@frequentis.com> > wrote:
