Date: Thu, 02 Jul 2015 10:43:23 +0200 From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@des.no> To: Leif Pedersen <bilbo@hobbiton.org> Cc: Mark Felder <feld@freebsd.org>, "freebsd-security\@freebsd.org" <freebsd-security@freebsd.org> Subject: Re: Leap Second Message-ID: <86oajvvtjo.fsf@nine.des.no> In-Reply-To: <CAK-wPOjqZUPnWSbgXYt%2Bghu1BHUK7E=dUVU=oW8%2B0p7ywzN4Wg@mail.gmail.com> (Leif Pedersen's message of "Wed, 1 Jul 2015 12:46:21 -0500") 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>
next in thread | previous in thread | raw e-mail | index | archive | help
Leif Pedersen <bilbo@hobbiton.org> writes: > Is there a reasonable way to enable awareness of leap-seconds while > syncing with ntpd? That is to say, how can I get the system to include > leap-seconds in calculating `date +%s`, without having `date` be off > by 26[1] seconds? No. POSIX deals with leap seconds by pretending they don't exist. > I tried setting /etc/localtime to UTC including leap-seconds [...] > However, ntpd continues to sync the clock (from pool.ntp.org) in > ignorance of leap-seconds. [...] Can ntpd undo the leap-seconds > inserted by ntp.org? Or is there another NTP pool that would work for > me? NTP works in UTC as well. The pool does not set the clock; all it does is coordinate servers who claim to know the correct time. I guess you could try to convince the ISC and JHU to add a TAI offset field to the next version of the NTP protocol... DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86oajvvtjo.fsf>