From owner-freebsd-cloud@freebsd.org Tue Dec 12 11:42:10 2017 Return-Path: Delivered-To: freebsd-cloud@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CBCABE95615 for ; Tue, 12 Dec 2017 11:42:10 +0000 (UTC) (envelope-from raf@rafal.net) Received: from fbo-1.mxes.net (mxout-23.mxes.net [216.86.168.223]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A49EC78260 for ; Tue, 12 Dec 2017 11:42:10 +0000 (UTC) (envelope-from raf@rafal.net) Received: from smtp-out-1.mxes.net (smtp-out-1.mxes.net [67.222.241.250]) by fbi-1.mxes.net (Postfix) with ESMTP id C999E27561 for ; Tue, 12 Dec 2017 06:35:57 -0500 (EST) Received: from [192.168.40.23] (86-40-118-125-dynamic.agg2.bri.bbh-prp.eircom.net [86.40.118.125]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id C7AE827551 for ; Tue, 12 Dec 2017 06:35:49 -0500 (EST) From: Rafal Lukawiecki Mime-Version: 1.0 (1.0) Date: Tue, 12 Dec 2017 11:35:48 +0000 Subject: AWS ntpd vs chrony Message-Id: To: freebsd-cloud@freebsd.org X-Mailer: iPad Mail (15C114) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-cloud@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "FreeBSD on cloud platforms \(EC2, GCE, Azure, etc.\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Dec 2017 11:42:10 -0000 I see from Colin=E2=80=99s commit https://lists.freebsd.org/pipermail/svn-sr= c-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 t= his 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 a= bove commit in preference to chrony. I have always relied on ntpd, and its p= redecessors, and I am new to chronyd, so I also wonder if there are advantag= es to using chrony in the AWS environment (web heads and application servers= mainly). Many thanks, Rafal -- Rafal Lukawiecki=