[181440] in North American Network Operators' Group
RE: REMINDER: LEAP SECOND
daemon@ATHENA.MIT.EDU (Matthew Huff)
Wed Jun 24 15:11:36 2015
X-Original-To: nanog@nanog.org
From: Matthew Huff <mhuff@ox.com>
To: Tore Anderson <tore@fud.no>
Date: Wed, 24 Jun 2015 19:11:33 +0000
In-Reply-To: <20150624210719.0f237d7c@envy.fud.no>
Cc: nanog2 <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
I saw that, but it says the bits are set "before 23:59" on the day of inser=
tion, but I was hoping that I could shut it down later than 23:59:59 of the=
previous day (8pm EST). The reason is FINRA regulations. We have to have t=
he time synced once per trading day before the open according to the regula=
tions.=20
We could manually run ntpdate on 100+ servers including 50+ windows servers=
, but that's not a great solution.
----
Matthew Huff=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 | 1 Manhattanville Rd
Director of Operations=A0=A0=A0| Purchase, NY 10577
OTA Management LLC=A0=A0=A0=A0=A0=A0 | Phone: 914-460-4039
aim: matthewbhuff=A0=A0=A0=A0=A0=A0=A0 | Fax:=A0=A0 914-694-5669
-----Original Message-----
From: Tore Anderson [mailto:tore@fud.no]=20
Sent: Wednesday, June 24, 2015 3:07 PM
To: Matthew Huff
Cc: nanog2
Subject: Re: REMINDER: LEAP SECOND
* Matthew Huff
> Does anyone know what the latest that we can run our NTP servers and
> not distribute the LEAP_SECOND flag to the NTP clients?
From http://support.ntp.org/bin/view/Support/NTPRelatedDefinitions:
Leap Indicator
This is a two-bit code warning of an impending leap second to be
inserted in the NTP timescale. The bits are set before 23:59 on the
day of insertion and reset after 00:00 on the following day. This
causes the number of seconds (rollover interval) in the day of
insertion to be increased or decreased by one.=20
So the answer to your question is, AIUI, 2015-06-29 23:59:59.
Tore
