nanog mailing list archives
Re: REMINDER: LEAP SECOND
From: shawn wilson <ag4ve.us () gmail com>
Date: Tue, 23 Jun 2015 13:23:04 -0400
On Jun 23, 2015 6:26 AM, "Nick Hilliard" <nick () foobar org> wrote:
Blocking NTP at the NTP edge will probably work fine for most situations. Bear in mind that your NTP edge is not necessarily the same as your
network
edge. E.g. you might have internal GPS / radio sources which could unexpectedly inject the leap second. The larger the network, the more likely this is to happen. Most organisations have network fossils and ntp is an excellent source of these. I.e. systems which work away for years without any problems before one day accidentally triggering meltdown because some developer didn't understand the subtleties of clock
monotonicity.
NTP causes jumps - not skews, right?
Current thread:
- Re: REMINDER: LEAP SECOND, (continued)
- Re: REMINDER: LEAP SECOND Baldur Norddahl (Jun 19)
- Re: REMINDER: LEAP SECOND Harlan Stenn (Jun 19)
- Re: REMINDER: LEAP SECOND Mel Beckman (Jun 19)
- Re: REMINDER: LEAP SECOND Harlan Stenn (Jun 20)
- Re: REMINDER: LEAP SECOND Doug Barton (Jun 22)
- Re: REMINDER: LEAP SECOND Harlan Stenn (Jun 22)
- Re: REMINDER: LEAP SECOND Mel Beckman (Jun 23)
- Re: REMINDER: LEAP SECOND Harlan Stenn (Jun 23)
- Re: REMINDER: LEAP SECOND Mel Beckman (Jun 23)
- Re: REMINDER: LEAP SECOND Nick Hilliard (Jun 23)
- Re: REMINDER: LEAP SECOND shawn wilson (Jun 23)
- Re: REMINDER: LEAP SECOND Jared Mauch (Jun 23)
- Re: REMINDER: LEAP SECOND Nick Hilliard (Jun 23)
- Re: REMINDER: LEAP SECOND Harlan Stenn (Jun 23)
- Re: REMINDER: LEAP SECOND Matthew Huff (Jun 23)
- Re: REMINDER: LEAP SECOND Harlan Stenn (Jun 23)
- Re: REMINDER: LEAP SECOND Tore Anderson (Jun 23)
- Re: REMINDER: LEAP SECOND Philip Homburg (Jun 24)
- Re: REMINDER: LEAP SECOND Tony Finch (Jun 24)
- Re: REMINDER: LEAP SECOND Philip Homburg (Jun 24)
- Re: REMINDER: LEAP SECOND Majdi S. Abbas (Jun 24)