Neither my problem nor his problem!
What do you see if you run something like this?
root@OpenWrt:~# /usr/sbin/ntpd -d -d -d -w -p 0.uk.pool.ntp.org
I get this:
ntpd: '0.uk.pool.ntp.org' is 82.219.4.30
ntpd: sending query to 82.219.4.30
ntpd: reply from 82.219.4.30: offset:+0.006744 delay:0.015886 status:0x24 strat:2 refid:0xb986c4a9 rootdelay:0.027451 reach:0x01
ntpd: no valid datapoints, no peer selected
ntpd: poll:2s sockets:0 interval:1s
ntpd: sending query to 82.219.4.30
ntpd: poll:16s sockets:1 interval:1s
Is it true that ntpd is only used by the client? That is, I don’t need to make any changes, he will make updates within this period of time.
NTP is adaptive .
Usually the clock is Synced once at startup.
Ntp then tries keep an accurate clock by essentially measuring the drift between the local clock and the servers clock. It then tweaks the frequency of the local to slowly reduce the drift between the two clocks.
If the the local or server clock is of poor quality it may never achieve proper sync.
2 Likes
Thank you, I always thought that you need to manually configure and synchronize the time interval
If your problem is solved, please consider marking this topic as [Solved]. See How to mark a topic as [Solved] for a short how-to.
1 Like
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.