[154366] in North American Network Operators' Group
Re: F-ckin Leap Seconds, how do they work?
daemon@ATHENA.MIT.EDU (Owen DeLong)
Tue Jul 3 05:06:54 2012
From: Owen DeLong <owen@delong.com>
In-Reply-To: <878vf1i5sb.fsf@arbol.wsrcc.com>
Date: Tue, 3 Jul 2012 02:03:10 -0700
To: "Wolfgang S. Rupprecht" <wolfgang.rupprecht@gmail.com>
Cc: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
DST is a time-zone specific phenomenon.
Leap seconds are changes to the actual core time. UTC moves with leap =
seconds.
It doesn't move with DST or other timezone weirdnesses.
The system clock needs to be UTC, not UTC =B1 some offset stuck =
somewhere that keeps some form of running tally of the current leap =
second offset since the epoch.
Owen
On Jul 3, 2012, at 1:54 AM, Wolfgang S. Rupprecht wrote:
>=20
> Steven Bellovin <smb@cs.columbia.edu> writes:
>> See
>> =
http://landslidecoding.blogspot.com/2012/07/linuxs-leap-second-deadlocks.h=
tml
>=20
> Maybe we should stop wrenching the poor system time back and forth. =
We
> no longer add or subtract daylight savings time (or timezones) to the
> kernel time, why do we do it with leapseconds? We should really move
> the leapseconds correction into the display routines like DST and
> timezones already are. I believe the Olson time code already has =
ifdefs
> for doing this. I wonder why the system's internal time isn't run =
that
> way.
>=20
> -wolfgang
> --=20
> g+: https://plus.google.com/114566345864337108516/about
>=20
