On Mon, Nov 02, 2020 at 09:52:59PM +0000, Gary Buhrmaster wrote: > On Mon, Nov 2, 2020 at 9:36 PM Nico Kadel-Garcia <nkadel@xxxxxxxxx> wrote: > > > So, use "chrony" instead? > > For some use cases, there is also the option of > systemd-timesyncd as a ntp client. timesyncd is a very minimal NTP client. It can be recommended in some specific use cases, like a local network with a trusted server, but not in the most common case of a client using random public servers on Internet. There are other minimal clients that should be considered before timesyncd, e.g. openntpd or the busybox ntpd. > > and can the ntp.conf files be ported gracefully to a > > compatible chrony.conf setting? In the vast majority of cases, yes, it can. There is even a ntp2chrony script for automatic conversion. The most common thing that people seem to miss is the mode-6 protocol, which is needed by some monitoring tools. That won't be supported in chrony, but it is in ntpsec. Autokey has been superseded by NTS. Broadcast/multicast modes are better supported by PTP (linuxptp). > If you are using hardware to discipline your server > using one/more of the hardware specific drivers > things get more complicated. Reference clocks shouldn't be a big issue. The refclock drivers from ntp will stay in Fedora, at least for now, in the ntp-refclock package. In future it might need to be switched to the ntpsec drivers. For GPS receivers, which are by far the most common reference clocks, there is also gpsd. -- Miroslav Lichvar _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
