[ntp:questions] ntpd on busybox ARM system not keeping time with server
David Woolley
david at ex.djwhome.demon.invalid
Tue May 18 11:56:45 UTC 2021
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.
> 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.
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.
More information about the questions
mailing list