ntpd question

I wrote:
>
> So it seems that it may be seeing 3 servers. I'll let it run for
> a few hours to see if the drift entry changes.
>
> Thanks a whole lot.

OK, the drift entry is now 1.211 whereas it was always
0.00 before. Progress.

On Mon, 2 Nov 2009 14:00:14 +0000 (UTC),
root <NoEMail.RemoveThis@home.org> wrote:
> Thomas Ronayne <trona.RemoveThis@ameritech.net> wrote:
>> Hope this helps some.
>
> I think it was a big help. I get this in the log file
> after re-starting ntpd:
> 2 Nov 05:51:24 ntpd[3077]: logging to file /tmp/ntp.log
> 2 Nov 05:51:24 ntpd[3077]: precision = 4000.000 usec
> 2 Nov 05:51:24 ntpd[3077]: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16
> 2 Nov 05:51:24 ntpd[3077]: Listening on interface #0 wildcard, 0.0.0.0#123 Disabled
> 2 Nov 05:51:24 ntpd[3077]: Listening on interface #1 lo, 127.0.0.1#123 Enabled
> 2 Nov 05:51:24 ntpd[3077]: Listening on interface #2 eth0, 10.0.0.3#123 Enabled
> 2 Nov 05:51:24 ntpd[3077]: kernel time sync status 0040
> 2 Nov 05:51:25 ntpd[3077]: frequency initialized 1.211 PPM from /etc/ntp/drift
> 2 Nov 05:54:41 ntpd[3077]: synchronized to LOCAL(0), stratum 10
> 2 Nov 05:54:41 ntpd[3077]: kernel time sync status change 0001
>
> and I get this for ntpq -p:
> remote refid st t when poll reach delay offset jitter
>==============================================================================
> *LOCAL(0) .LOCL. 10 l 46 64 77 0.000 0.000 3.906
> clock.team-cymr 192.168.0.16 2 u 47 64 77 67.367 27839.7 2012.35
> lime7.adamantsy 208.75.88.4 3 u 41 64 77 48.759 27902.8 2043.38
> rrcs-64-183-56- .GPS. 1 u 50 64 77 23.623 27810.4 1974.96
>
> So it seems that it may be seeing 3 servers. I'll let it run for
> a few hours to see if the drift entry changes.

Looks good. As the time synchronization is refined you should see
the polling frequency decrease until it hits a 1024 second period.
Example follows:

sys cloc = Mon Nov 2 11:47:01 EST 2009
remote refid st t when poll reach delay offset jitter
==============================================================================
LOCAL(0) LOCAL(0) 7 l 59 64 377 0.000 0.000 0.001
+ns4.usg.edu 130.207.244.240 2 u 140 1024 377 87.608 -5.236 10.040
*ntp-1.gw.uiuc.e 128.174.38.133 2 u 274 1024 377 42.845 1.167 0.302
+ntp-2.gw.uiuc.e 128.174.38.133 2 u 165 1024 377 40.405 1.512 0.010
-caesar.cs.wisc. 128.105.201.11 2 u 103 1024 377 66.877 13.913 0.360
-dr-zaius.cs.wis 128.105.201.11 2 u 211 1024 377 64.500 11.970 0.851
+hickory.cc.colu 128.59.39.48 2 u 33 1024 377 74.594 2.175 3.762

I find the ntp logs informative on my connectivity and also on
gross network congestion.

--
Theodore (Ted) Heise <theo.RemoveThis@heise.nu> Bloomington, IN, USA