Re: ntpd

Hi Bob

Am 12.05.2022 um 09:36 schrieb Bob von Knobloch:
...>
> I restarted ntpd yesterday, but saw no change. This morning, however,
> the time has corrected itself - oh well!

Oh well, now there is little chance to find the problem. Still as your 
system clock drifted off quite far it appears that it did not receive 
suitable time information.

To find out more you should use ntpq. It will enable you to see what 
peers your ntp daemon is talking to and will also tell you about offset 
and jitter and stratum.

SALT# ntpq
ntpq> peers
      remote           refid      st t when poll reach   delay   offset 
  jitter
==============================================================================
  ntp20.kashra-se 192.168.100.15   2 u  153  128    1  151.381   43.453 
   0.031
  ntp2.tecnico.ul 56.99.239.27     2 u  157   64    1  483.811  -117.37 
   0.031
  88.157.128.22   212.113.174.246  3 u  155   64    1  716.136  -250.81 
   0.031
ntpq>

It is also a good idea to specify more than one time source like so:

# pool.ntp.org maps to more than 100 low-stratum NTP servers.
# Your server will pick a different set every time it starts up.
#  *** Please consider joining the pool! ***
#  ***  <http://www.pool.ntp.org/#join>  ***
#server luna.think.ch iburst
server europe.pool.ntp.org iburst
server 0.pool.ntp.org
server 1.pool.ntp.org


cheers

ET

------------------------------------------------------------------------
leaf-user mailing list: [email protected]
https://lists.sourceforge.net/lists/listinfo/leaf-user
Support Request -- http://leaf-project.org/