On Tue, Sep 24, 2024 at 01:27:14 -0400, gene heskett wrote:
> I personally am running ntpsec here, making this box a level 2 src, and have
> redirected most of my machines to it. Nut as a client, ntpsec fails as it
> cannot slam the correct time at bootup, apparently only adjust drift. So
> clients should be using chrony, which can force time into sync while
> booting.
It works for everyone else.
hobbit:~$ ps -ef | grep ntpsec
ntpsec 855 1 0 Aug31 ? 00:01:50 /usr/sbin/ntpd -p
/run/ntpd.pid -c /etc/ntpsec/ntp.conf -g -N -u ntpsec:ntpsec
greg 575861 1226 0 07:04 pts/14 00:00:00 grep ntpsec
hobbit:~$ man ntpd
[...]
-g, --panicgate
Allow the first adjustment to be big. This option may appear an
unlimited number of times.
Normally, ntpd exits with a message to the system log if the offset
exceeds the panic threshold, which is 1000 s by default. This
option allows the time to be set to any value without restriction;
however, this can happen only once. If the threshold is exceeded
after that, ntpd will exit with a message to the system log. This
option can be used with the -q and -x options. See the tinker
configuration file directive for other options.
Maybe your NON-DEBIAN system configured something differently. We
don't know, because we run Debian here on this mailing list.
