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. > Is the functionality sufficient As always, given the different use cases, the answer is maybe. Here is a quick comparison: https://chrony.tuxfamily.org/comparison.html > and can the ntp.conf files be ported gracefully to a > compatible chrony.conf setting? Again, it would depend on how you are using ntpd. For the cases where the system is just a client of the protocol trying keep the right time, it should be easy to migrate to either chrony (or systemd-timesyncd). If you are using hardware to discipline your server using one/more of the hardware specific drivers things get more complicated. _______________________________________________ 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
