You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you use the servers directive, the initial time setting is not working.
For example if you use the following config:
servers 0.de.pool.ntp.org trusted
Ntp will print:
bash-5.1# ntpd -d -f ntpd.conf
/var/db/ntpd.drift is empty
ntp engine ready
peer 185.120.22.12 now valid
peer 87.106.180.117 now valid
peer 217.197.91.176 now valid
peer 164.68.116.11 now valid
no reply received in time, skipping initial time setting
Important to note is that the traffic is not blocked and even more imported is that if you switch from servers to server, everything is working. Like:
bash-5.1# ntpd -d -f ntpd.conf
/var/db/ntpd.drift is empty
ntp engine ready
peer 185.120.22.14 now valid
set local clock to Tue Aug 30 11:58:58 UTC 2022 (offset 20780872.936448s)
The text was updated successfully, but these errors were encountered:
If you use the
servers
directive, the initial time setting is not working.For example if you use the following config:
Ntp will print:
Important to note is that the traffic is not blocked and even more imported is that if you switch from servers to server, everything is working. Like:
The text was updated successfully, but these errors were encountered: