[time-nuts] Leap second glitches on NTP using Z3801A

[Brooke Clarke]

Hi Eric:

So that you can figure out UTC.  But there's no DST bit on any of the 
satellites so for that you need a local time broadcast.


Have Fun,

Brooke Clarke
http://www.prc68.com

Eric Garner wrote:
> Ascending from Lurk Mode, I have a (possibly stupid) question: according to
> 
> http://tycho.usno.navy.mil/leapsec.html
> 
> and Tony Jones's book "The Story of Atomic Time" GPS time does not
> account for leap seconds, So why does it alert you to them?
> 
> -eric
> 
> On Sun, Nov 16, 2008 at 7:21 PM, Hal Murray <hmurray at megapathdsl.net> wrote:
>> Is anybody running ntpd with their Z3801A?
>>
>> If so, please check your log files and tell me if you see a bogus leap second
>> at the end of the past several months.  I've seen them for Aug, Sep, and Oct.
>>  I think they are coming from my Z3801A, but it might be something else.
>>
>> The GPS satellites are now announcing a leap second that will happen at the
>> end of the year.   The refclock driver passes that to ntpd and ntpd passes it
>> to the kernel and magic happens.
>>
>> I think the refclock-ntpd interface assumes the leap second will happen at
>> the end of the current month.  NIST only announces leap seconds a month ahead
>> on WWVB and ACTS.
>>
>> The Oncore refclock driver has a filter to wait until the current month to
>> pass the info to ntpd.  I'm working on something similar for the HP driver.
>>
>> --
>> These are my opinions, not necessarily my employer's.  I hate spam.
>>
>>
>>
>>
>> _______________________________________________
>> time-nuts mailing list -- time-nuts at febo.com
>> To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
>> and follow the instructions there.
>>
> 
> 
>