[ntp:questions] picking a system peer

Jason Rabel jason at extremeoverclocking.com
Sat Aug 18 00:14:24 UTC 2007


Your GPS offset is almost a second off... Thus it fails the sanity checks
and is discarded.

Which GPS receiver do you have specifically?

http://www.ece.udel.edu/~mills/ntp/html/drivers/driver26.html

If you have a Z3801A (or similar), did you add the "mode 1" on the server
config line? And did you follow the suggestions for the proper "fudge"
factor?

Jason 


> Next issue: ntpd consistently does not pick the local GPS receiver as
> system peer and instead locks in on another server with higher delay and
> stratum.

....

> The first server is my GPS receiver. The next three are open stratum 1
> servers. The final two are open stratum 2 servers.

> After ntpd has run for around 24 hours, ntpq -p looks like this:

> mail# ntpq -p
>      remote           refid      st t when poll reach   delay   offset
> jitter
>
============================================================================
==
> xGPS_HP(0)       .GPS.            0 l   11   64  377    0.000  947.161
>  3.081
> +timekeeper.isi. .GPS.            1 u  845 1024  237   61.107   -4.727
>  7.175
> +cpe-76-168-23-8 .GPS.            1 u   67 1024  377   34.322   -3.144
>  1.387
> *cpe-76-169-239- .GPS.            1 u  103 1024  377   29.793    0.814
>  3.152
> - -hydrogen.cert.u 216.218.254.202  2 u   57 1024  377   14.689   -3.012
>  4.311
> - -clock-b.develoo 10.0.201.116     2 u 1021 1024  377   18.789   -3.747
>  0.439




More information about the questions mailing list