[LEAPSECS] W1K GPS rollover for some time servers

Alex Currant alexcurrant911 at yahoo.com
Sun May 3 22:01:15 EDT 2015


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 <sla at ucolick.org>
 To: Leap Second Discussion List <leapsecs at leapsecond.com> 
 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                <sla at ucolick.org>              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
LEAPSECS at leapsecond.com
https://pairlist6.pair.net/mailman/listinfo/leapsecs


  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist6.pair.net/pipermail/leapsecs/attachments/20150504/0fe3db62/attachment.html>


More information about the LEAPSECS mailing list