[181431] in North American Network Operators' Group
Re: REMINDER: LEAP SECOND
daemon@ATHENA.MIT.EDU (Matthew Huff)
Wed Jun 24 08:34:10 2015
X-Original-To: nanog@nanog.org
From: Matthew Huff <mhuff@ox.com>
To: Harlan Stenn <stenn@ntp.org>
Date: Wed, 24 Jun 2015 12:34:05 +0000
In-Reply-To: <E1Z7bQv-000Nil-J5@stenn.ntp.org>
Cc: nanog2 <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
Yes, the clock has to be bad. Been there, done that, especially early Sun x=
86 servers.
Leap years and DST are both things people and developers are aware of outsi=
de of technology, leap seconds, not so much.
> On Jun 23, 2015, at 11:33 PM, Harlan Stenn <stenn@ntp.org> wrote:
>=20
> Matthew Huff writes:
>> A backward step is a known issue and something that people are more
>> comfortable dealing with as it can happen on any machine with a noisy
>> clock crystal.
>=20
> A clock crystal has to be REALLY bad for ntpd to need to step the clock.
>=20
>> Having 61 seconds in a minute or 86401 seconds in a day is a different
>> story.
>=20
> Yeah, leap years suck too.
>=20
> And those jumps around daylight savings time.
>=20
> H
