The point is that any complication is a potential source of programming errors,
and any potential source will eventually lead to problems in predictable and
unpredictable ways. The W1K problem is one example. Leap seconds are
another.
From: Steve Allen <[email protected]>
To: Leap Second Discussion List <[email protected]>
Sent: Sunday, May 3, 2015 7:52 PM
Subject: [LEAPSECS] W1K GPS rollover for some time servers
As seen at
http://lists.ntp.org/pipermail/hackers/2015-May/006866.html
and also as experienced at Keck Observatory last night, some models
of GPS time servers just did their firmware's W1K rollover, so those
are saying the date is 1995-09-17.
But the leap second is, inappropriately, getting the blame!
--
Steve Allen <[email protected]> WGS-84 (GPS)
UCO/Lick Observatory--ISB Natural Sciences II, Room 165 Lat +36.99855
1156 High Street Voice: +1 831 459 3046 Lng -122.06015
Santa Cruz, CA 95064 http://www.ucolick.org/~sla/ Hgt +250 m
_______________________________________________
LEAPSECS mailing list
[email protected]
https://pairlist6.pair.net/mailman/listinfo/leapsecs
_______________________________________________
LEAPSECS mailing list
[email protected]
https://pairlist6.pair.net/mailman/listinfo/leapsecs
