Charles R. Anderson wrote:
That isn't a fix. In fact, if you remove that, ntpd might not even
start if your local clock is too far off.
No, because then the -g option is added.
-g Normally, ntpd exits if the offset exceeds the sanity limit,
which is 1000 s by default. If the sanity limit is set to
zero, no sanity checking is performed and any offset is
acceptable. This option overrides the limit and allows the
time to be set to any value without restriction; however, this
can happen only once. After that, ntpd will exit if the
limit is exceeded. This option can be used with the -q
option.
