23 Jun
2015
23 Jun
'15
1:23 p.m.
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?