[time-nuts] Testing frequency using NTP

[Steve Rooke]

Your results are considerably better than mine but these are just off
my busy workstation taken as a snapshot. I have no local time standard
so dependant on the external servers. Perhaps I could do better on a
dedicated system running a RT Linux:-

ntpdc> peers
     remote           local      st poll reach  delay   offset    disp
=======================================================================
=LOCAL(0)        127.0.0.1       10   64  377 0.00000  0.000000 0.03079
=infinite-loop.n 192.168.0.2      2 1024  377 0.08951  0.010470 0.13661
*gen2.ihug.co.nz 192.168.0.2      2 1024  377 0.06548  0.008092 0.13657
=mu-relay2.masse 192.168.0.2      2 1024  377 0.10503  0.003384 0.13667
=ns2.compass.net 192.168.0.2      2 1024  377 0.06645 -0.007766 0.12173
ntpdc>

Over a long sampling time though, these errors should factor out to be
very small anyway.

Cheers,
Steve

2008/10/2 Björn Gabrielsson <bg at lysator.liu.se>:
> You do not have to chose a bad NTP server. With better servers you can
> gain a few orders of magnitude.
>
> $ ntpq -p timehost.lysator.liu.se
>
>     remote           refid      st ...  delay   offset  jitter
> ================================================================
> *GENERIC(0)      .GPS.            0 ...   0.000    0.014   0.002
> +nissan.ifm.liu. .PPS.            1 ...   0.651    0.000   0.035
> +ntp1.sth.netnod .PPS.            1 ...   3.667   -0.018   0.052
> +ntp2.gbg.netnod .PPS.            1 ...  10.967   -0.010   0.014
> -ntp1.mmo.netnod .PPS.            1 ...  13.899   -0.077   0.061
>
> Also look at the NTP temperature compensation discussion at
>
>    http://www.ijs.si/time/temp-compensation/
>
>
> --
>
>    Björn
>
>
> _______________________________________________
> 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.



-- 
Steve Rooke - ZL3TUV & G8KVD
Omnium finis imminet