[154371] in North American Network Operators' Group
Re: F-ckin Leap Seconds, how do they work?
daemon@ATHENA.MIT.EDU (Joel jaeggli)
Tue Jul 3 10:06:23 2012
Date: Tue, 03 Jul 2012 07:02:33 -0700
From: Joel jaeggli <joelja@bogus.com>
To: "Wolfgang S. Rupprecht" <wolfgang.rupprecht@gmail.com>
In-Reply-To: <878vf1i5sb.fsf@arbol.wsrcc.com>
Cc: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On 7/3/12 01:54 , Wolfgang S. Rupprecht wrote:
>
> Steven Bellovin <smb@cs.columbia.edu> writes:
>> See
>> http://landslidecoding.blogspot.com/2012/07/linuxs-leap-second-deadlocks.html
>
> 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.
Neither timezones nor dst impact length of the mean solar day.
TAI is some 35 seconds ahead of UTC this point. and will continue to
diverge in a fashion which is not sufficiently predictable that you can
know over the long term.
Not using utc as the timebase is certainly possible, gps does that for
example.
Apps are buggy sounds like a really poor excuse for doing so.
> -wolfgang
>
