Date: Tue, 12 Dec 2017 11:35:48 +0000 From: Rafal Lukawiecki <raf@rafal.net> To: freebsd-cloud@freebsd.org Subject: AWS ntpd vs chrony Message-ID: <F2557D60-B298-48F8-A20F-F8373F48C5B0@rafal.net>
next in thread | raw e-mail | index | archive | help
I see from Colin’s commit https://lists.freebsd.org/pipermail/svn-src-head/2017-December/106978.html that AWS FreeBSD AMIs will be configured to use the new API to NTP via 169.254.169.123 host/interface. AWS are baking this into AML using chronyd rather than ntpd. I realise that ntpd comes with FreeBSD, and I was wondering if that was the reason it has been used in the above commit in preference to chrony. I have always relied on ntpd, and its predecessors, and I am new to chronyd, so I also wonder if there are advantages to using chrony in the AWS environment (web heads and application servers mainly). Many thanks, Rafal -- Rafal Lukawiecki
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?F2557D60-B298-48F8-A20F-F8373F48C5B0>