[LinuxPPS] ntp: add hardpps implementation

Udo van den Heuvel udovdh at xs4all.nl
Sun Oct 10 18:56:01 CEST 2010


On 2010-10-10 18:48, Remco dB wrote:
> On Sunday 10 October 2010 17:29:30 Udo van den Heuvel wrote:
> 
> 
>> [root at epia tor]# ntpq -pn
>>      remote           refid      st t when poll reach   delay   offset
>> jitter
>> ===========================================================================
>> === o127.127.20.0    .GPS.            0 l    6   16  377    0.000    0.006
>>  0.002
(...)
>> *83.163.219.98   .DCFa.           1 u   63   64  377   41.072   -9.059
>>  6.893
> 
> I have a similar list, but what surprises me is that in your (and mine with 
> hardpps) list TWO machines seem to be the 'preferred' peer, i.e. *83.163 (with 
> a star) and your oATOM (127.127.20.0) :

o is PPS source being used.
* is alternative `if somethign happens`?

> and not a list both both a '*' and 'o'

I don't think this is a hardpps() issue but perhaps the way ntpd works
as that program does the decisionmaking. (but I could be wrong)
Maybe go online and check #ntp on freenode?

Udo



More information about the LinuxPPS mailing list