Date: Wed, 1 Jul 2015 21:52:46 -0400 From: Garrett Wollman <wollman@bimajority.org> To: Peter Jeremy <peter@rulingia.com> Cc: "freebsd-security@freebsd.org" <freebsd-security@freebsd.org> Subject: Re: Leap Second Message-ID: <21908.39278.416719.875140@hergotha.csail.mit.edu> In-Reply-To: <20150701202728.GA9532@server.rulingia.com> References: <CAA3htvuv0Emy5SazXzYNZegKzS-Z4=tc3ua8Ca6GMgeTj99n7A@mail.gmail.com> <1435154274.964221.306546033.052903CD@webmail.messagingengine.com> <86bnfwxa4m.fsf@nine.des.no> <1435758941.105242.312562265.3103CECB@webmail.messagingengine.com> <CAK-wPOjqZUPnWSbgXYt%2Bghu1BHUK7E=dUVU=oW8%2B0p7ywzN4Wg@mail.gmail.com> <20150701202728.GA9532@server.rulingia.com>
next in thread | previous in thread | raw e-mail | index | archive | help
<<On Thu, 2 Jul 2015 06:27:28 +1000, Peter Jeremy <peter@rulingia.com> said: > ntpd(8) has provision for specifying a leapsecond file which presumably > makes it leap-second aware. I haven't looked into the details. The current NTP protocol, as implemented by ntpd, distributes leap-second information if provided. This information may be provided by higher-stratum (upstream) NTP servers, or by using the "leapfile" configuration statement in ntp.conf to specify a local copy of the leapseconds file in NIST/USNO format. No such file is provided by default. We could easily do so, but shouldn't, because that file would take precedence over the leap indicator learned from higher-stratum servers, and that's not desirable for clients. If you're running a bunch of servers, you should distribute and install the leapseconds file using your configuration-management system. (For example, my puppet module for NTP, which we use at CSAIL for three NTP servers, does so: <https://github.com/gwollman/puppet-ntp>.) -GAWollman
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?21908.39278.416719.875140>