Re: ntp(d) on Boot Behavior

2022-11-07 Thread Stuart Henderson
On 2022-11-07, indivC wrote: > Would the correct place to do this be in /etc/rc > and rdate(8) should be called right before it says > "echo -n 'starting early daemons:'"? > Or is there a better way of doing this? That's probably the most correct place, but I don't like modifying /etc/rc if avoid

Re: ntp(d) on Boot Behavior

2022-11-06 Thread indivC
Stuart, I am aware that ntpd(8) on boot won't update the clock if the current time is ahead of the time received from the time server. It's in the man page section that I posted in my message. I personally have never really had an issue there, though. I'm aware of a variety of ways to resolve the

Re: ntp(d) on Boot Behavior

2022-11-06 Thread Stuart Henderson
On 2022-11-06, indivC wrote: > I could be wrong, but I believe there's another condition > that isn't mentioned. > As far as I can tell, if the clock is behind less than 60 seconds, > ntpd will not update the clock. Same if the clock is *ahead* of NTP time. You can ensure that the clock is cl

Re: ntp(d) on Boot Behavior

2022-11-06 Thread Otto Moerbeek
On Sun, Nov 06, 2022 at 05:06:57PM +, indivC wrote: > The ntpd man page says the following: > 'ntpd will stay for a maximum of 15 seconds in the foreground > and make efforts to verify and correct the time > if constraints are configured and satisfied or > if trusted servers or sensors return

ntp(d) on Boot Behavior

2022-11-06 Thread indivC
The ntpd man page says the following: 'ntpd will stay for a maximum of 15 seconds in the foreground and make efforts to verify and correct the time if constraints are configured and satisfied or if trusted servers or sensors return results, and if the clock is not being moved backwards.'. I could