[ntp:questions] Peer Review of ntpq -c rv

Chuck Swiger cswiger at mac.com
Wed Mar 7 16:46:05 UTC 2012


On 3/7/2012 11:15 AM, Alby VA wrote:
> Here is my ntpq -p  output:
>
> [alby at godzilla.empire.org(tcsh):6] ntpq -p
>       remote           refid      st t when poll reach   delay
> offset  jitter
> ==============================================================================
> -ntp.alaska.edu  .GPS.            1 u  133  128  377  120.428
> -2.464   0.371
> +utcnist2.colora .ACTS.           1 u   53  128  377   66.362
> -4.215   0.429
> -time-a.nist.gov .ACTS.           1 u  670  128  240   16.473
> 2.627  17.066
> +tick.usask.ca   .GPS.            1 u  110  128  377  104.848
> -3.473   1.482
> -cronos.cenam.mx .GPS.            1 u   49  128  377  100.163
> 10.784  27.096
> oPPS(0)          .PPS.            0 l    6   16  377    0.000
> -0.018   0.002
> *GPS_NMEA(0)     .GPSb.           0 l    9   16  377    0.000
> -36.164  18.050
> [alby at godzilla.empire.org(tcsh):7]

OK, you're seeing valid PPS lock, which is good.

But most of the remote NTP servers you are querying have relatively long 
delays; only utcnist2.colora and time-a.nist.gov are reasonably close in terms 
of delay.  Drop the others and find some other timeservers with lower ping/ntp 
query times, even if they are stratum-2 or higher.

Regards,
-- 
-Chuck



More information about the questions mailing list