Re: ntpd

On Thursday, 12 May 2022 5:25:12 PM AEST Bob von Knobloch wrote:
> On 12/05/2022 03:23, marko via leaf-user wrote:
> > On Wednesday, 11 May 2022 11:20:38 PM AEST Bob von Knobloch wrote:
> >> Hi, I am using LEAF (2 boxes) as VPN entry points. While checking
> >> connectivity to a client, I noticed that the time was ca. 40 minutes
> >> slow.
> >> ntpd is installed and configured.
> >> I am sure that a reboot would set the time, but it would be nice to do
> >> this by hand. Does the LEAF ntpd have a way of manually setting and why
> >> is the time drifting so ?
> > 
> > NTPD won't set the system clock if there is too much time difference.  
> > It's the "-g" option that allows sync regardless of the system clock time
> > at boot.
> > 
> > To answer your direct question, set the system clock close to the right
> > time using "date" and NTPD will take over maintaining it.
> > 
> > cheers
> > 
> > Marko
> 
> A good thought Marko, I'll try it as a temporary cure.
> These boxes 'never' get rebooted, but why has the time diverged?
> Time sync was OK when I installed them and, as Erich wrote "NTPD is
> supposed to run seamlessly"
> 
> Bob


I run a stratum 1 time server here as part of ntppool.  NTPD on leaf  is the 
time server to the outside world.  I would agree that NTPD is supposed to run 
seamlessly, but observe that it does not like disconnection to it's primary 
time source.   When there is a connection problem, I always have to restart 
NTPD.  For this reason, Stratum 1 runs Chronyd, stratum 2 public use NTPD.  





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