[154453] in North American Network Operators' Group
Re: F-ckin Leap Seconds, how do they work?
daemon@ATHENA.MIT.EDU (Steve Allen)
Wed Jul 4 11:58:55 2012
From: Steve Allen <sla@ucolick.org>
In-Reply-To: <CAAAwwbXX1A+vrcwojjWL00oxVFOGHnUHfK1G=tHzkby+SVqsQA@mail.gmail.com>
Date: Wed, 4 Jul 2012 08:58:11 -0700
To: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On 2012 Jul 4, at 08:50, Jimmy Hess wrote:
> So accept the inaccuracy and correct the clock in the normal way that
> NTP corrects clocks that have drifted.
This is basically the "leap smear" that google instituted after
the issues in 2005. It works nicely in cloud applications where
real-time is not an issue. It does not work so well when precision
calculations of real-time physics are important, nor in heterogeneous
environments where not all devices pay attention to NTP or some
handle the leap differently than others. Those are places
where a kernel should never be asked to do what the combination
of POSIX and leap seconds demand.
=
=20
--
Steve Allen <sla@ucolick.org> WGS-84 (GPS)
UCO/Lick Observatory Natural Sciences II, Room 165 Lat +36.99855
University of California Voice: +1 831 459 3046 Lng -122.06015
Santa Cruz, CA 95064 http://www.ucolick.org/~sla/ Hgt +250 m
