Otto Moerbeek wrote:
1. Test the diff below
Thanks Otto,
That diff definitely help and fix the problem of clock that drift more
then what's allow to be corrected.
I tested it on two systems, both running current
OpenBSD 4.2-current (GENERIC) #0: Mon Dec 10 17:39:46 EST 2007
And the results are great. Sync fairly fast and stay sync and also more
importantly will actually be able to write the 'ntpd.drift' and then
keep going nicely.
See details in both test cases below from start to full sync and written
of the ntpd.drift file.
As you can see below, it needed to have a correction allow > then the
limit of 500 ppm. So, the 5000 now allow for quick catch up and then
keep it in sync as well.
Thanks
Daniel
Test server #1
Dec 10 18:08:29 ntp1a ntpd[8788]: ntp engine ready
Dec 10 18:08:47 ntp1a ntpd[8788]: peer 63.111.165.21 now valid
Dec 10 18:08:48 ntp1a ntpd[8788]: peer 217.160.254.116 now valid
Dec 10 18:08:48 ntp1a ntpd[8788]: peer 64.25.87.54 now valid
Dec 10 18:08:49 ntp1a ntpd[8788]: peer 208.122.38.159 now valid
Dec 10 18:08:51 ntp1a ntpd[8788]: peer 66.250.45.2 now valid
Dec 10 18:08:51 ntp1a ntpd[8788]: peer 131.128.170.235 now valid
Dec 10 18:08:51 ntp1a ntpd[8788]: peer 66.36.239.104 now valid
Dec 10 18:08:54 ntp1a ntpd[8788]: peer 217.160.252.91 now valid
Dec 10 18:08:54 ntp1a ntpd[8788]: peer 82.165.177.157 now valid
Dec 10 18:09:48 ntp1a ntpd[20604]: adjusting local clock by 1.083331s
Dec 10 18:11:25 ntp1a ntpd[20604]: adjusting local clock by 0.605259s
Dec 10 18:13:02 ntp1a ntpd[20604]: adjusting local clock by 0.205134s
Dec 10 18:16:08 ntp1a ntpd[20604]: adjusting local clock by 0.138711s
Dec 10 18:16:08 ntp1a ntpd[8788]: clock is now synced
Dec 10 18:20:26 ntp1a ntpd[20604]: adjusting local clock by 0.127213s
Dec 10 18:24:06 ntp1a ntpd[20604]: adjusting local clock by 0.196957s
Dec 10 18:24:36 ntp1a ntpd[20604]: adjusting local clock by 0.050985s
Dec 10 18:24:36 ntp1a ntpd[8788]: clock is now unsynced
Dec 10 18:25:10 ntp1a ntpd[8788]: clock is now synced
Dec 10 18:26:46 ntp1a ntpd[20604]: adjusting local clock by 0.076211s
Dec 10 18:28:56 ntp1a ntpd[20604]: adjusting local clock by 0.167692s
Dec 10 18:33:06 ntp1a ntpd[20604]: adjusting local clock by 0.115472s
Dec 10 18:34:44 ntp1a ntpd[20604]: adjusting local clock by 0.062104s
Dec 10 18:34:44 ntp1a ntpd[20604]: adjusting clock frequency by
697.957149 to 697.957149ppm
Dec 10 18:37:21 ntp1a ntpd[20604]: adjusting local clock by 0.090029s
=================================================
Test server #2
Dec 10 18:11:14 ntp1b ntpd[12948]: ntp engine ready
Dec 10 18:11:31 ntp1b ntpd[12948]: peer 64.25.87.54 now valid
Dec 10 18:11:34 ntp1b ntpd[12948]: peer 131.128.170.235 now valid
Dec 10 18:11:36 ntp1b ntpd[12948]: peer 66.36.239.104 now valid
Dec 10 18:11:36 ntp1b ntpd[12948]: peer 66.250.45.2 now valid
Dec 10 18:11:36 ntp1b ntpd[12948]: peer 217.160.254.116 now valid
Dec 10 18:11:36 ntp1b ntpd[12948]: peer 82.165.177.157 now valid
Dec 10 18:11:37 ntp1b ntpd[12948]: peer 208.122.38.159 now valid
Dec 10 18:11:37 ntp1b ntpd[12948]: peer 217.160.252.91 now valid
Dec 10 18:11:37 ntp1b ntpd[12948]: peer 63.111.165.21 now valid
Dec 10 18:12:31 ntp1b ntpd[32196]: adjusting local clock by 1.499023s
Dec 10 18:16:17 ntp1b ntpd[32196]: adjusting local clock by 0.448411s
Dec 10 18:20:33 ntp1b ntpd[32196]: adjusting local clock by 0.164415s
Dec 10 18:20:33 ntp1b ntpd[12948]: clock is now synced
Dec 10 18:24:23 ntp1b ntpd[32196]: adjusting local clock by 0.097930s
Dec 10 18:28:01 ntp1b ntpd[32196]: adjusting local clock by 0.178284s
Dec 10 18:33:31 ntp1b ntpd[32196]: adjusting local clock by 0.098047s
Dec 10 18:34:05 ntp1b ntpd[32196]: adjusting local clock by 0.063707s
Dec 10 18:37:49 ntp1b ntpd[32196]: adjusting local clock by 0.087770s
Dec 10 18:38:54 ntp1b ntpd[32196]: adjusting local clock by 0.043003s
Dec 10 18:38:54 ntp1b ntpd[32196]: adjusting clock frequency by
562.130055 to 562.130055ppm
