Jakob Bohm wrote:
On 2021-05-19 09:55, Terje Mathisen wrote:
Jakob Bohm wrote:
On 2021-05-18 13:56, David Woolley wrote:
On 18/05/2021 12:26, Andreas Schick wrote:
server 127.127.1.0 # local clock (LCL)
fudge 127.127.1.0 stratum 10 # LCL is unsynchronized
Delete these lines. As described, this system is not suitable as a
time server, and including these lines on a pure client can actually
frustrate synchronisation. This fake server is likely to vote
against the genuine server.
Perhaps the "tos orphan" option is a better way to make ntpd continue
after loss of all time sources.
Maybe some option to force treating the Windows server as stratum 12,
even if it looses outside synch and reports itself as stratum 16.
server 192.168.101.2
This appears to be the machine itself, so it will be voting that's
its own time is correct. Delete it.
Windows machines can vary from fair to atrocious as time servers. A
workstation running a default configuration of w32time will be at
the atrocious end.
Fortunately, this is reportedly a server, which means it will keep time
with a somewhat coarse granularity and include a battery backed TOY
(Time Of Year) clock to keep time even across power outages.
W32Time in server mode has a tendency to fluctuate about +/- 10ms from
the time sources. It is designed to provide an SNTP time source for
Kerberos clients that need to stay within +/- 5 minutes of the Kerberos
KDC.
You should make sure that the ARM starts in the right ball park, by
either using a file timestamp to record the time at, or close to,
shutdown, or, as a last resort, setting a fixed time that isn't too
far from reality.
Perhaps using the sntp program to do initial synchronization to the
server machine (as a better alternative to ntpd -g).
ntpd with iburst is pretty much always better, even more so when you
have multiple servers configured.
In my experience, ntpd algorithms converge very slowly in the trivial
cases where the initial local clock is not set, and all (or only in the
OPs case) sources agree on the correct time (TrueChimers).
Huh?
With an initial iburst I'm seeing 1-5s convergence.
Terje
--
- <Terje.Mathisen at tmsw.no>
"almost all programming can be viewed as an exercise in caching"
_______________________________________________
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions
