Date: Wed, 20 Feb 2019 00:09:09 +0000 From: Rafal Lukawiecki <raf@rafal.net> To: Colin Percival <cperciva@tarsnap.com> Cc: freebsd-cloud@freebsd.org Subject: Re: Duplicate entry in AWS FreeBSD 12.0 ntp.conf Message-ID: <2E3D9ACA-0ACE-4305-BE35-80B50236E154@rafal.net> In-Reply-To: <010001690816f97a-13e5dc2c-f96e-40fc-a3e2-65e7f5c9a7c6-000000@email.amazonses.com> References: <F2B8C2EA-2765-4320-8561-0818583176C3@rafal.net> <010001690816f97a-13e5dc2c-f96e-40fc-a3e2-65e7f5c9a7c6-000000@email.amazonses.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Thank you, Colin! Rafal > On 19 Feb 2019, at 23:28, Colin Percival <cperciva@tarsnap.com> wrote: > > On 2/19/19 2:48 PM, Rafal Lukawiecki wrote: >> I have just noticed that ntp.conf that comes in the AWS AMI for FreeBSD-12.0 (releng/12.0/usr.sbin/ntp/ntpd/ntp.conf 337649 2018-08-11 17:42:42Z brd) lists the AWS “server” twice, once on line 50, then again on line 96. I am not sure if that is on purpose, but it can lead to some confusion if one got changed but not the other. > > Oops. Not intentional, just an erroneous sed script. Fixed in r344315. > >> On another note, is there a reason to use chrony instead of ntpd if using the AWS ntp source, ie. 169.254.169.123? > > Nope. Chrony is what Amazon uses and it's what they recommend for anyone > starting from a blank slate; but I discussed this with them and they agreed > that since we ship with ntpd already installed it makes far more sense to > use what we already have. > > -- > Colin Percival > Security Officer Emeritus, FreeBSD | The power to serve > Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2E3D9ACA-0ACE-4305-BE35-80B50236E154>