Date: Wed, 05 Jun 2019 14:25:36 -0700 From: "Ronald F. Guilmette" <rfg@tristatelogic.com> To: freebsd-questions@freebsd.org Subject: Re: ntpd configutration -- a small suggestion from the peanut gallery Message-ID: <52802.1559769936@segfault.tristatelogic.com> In-Reply-To: <alpine.BSF.2.20.1906051648560.44637@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <alpine.BSF.2.20.1906051648560.44637@fledge.watson.org>,
doug@fledge.watson.org wrote:
>> Did I just miss those ntpd death messages somehow?
>
>I'm not sure. Somewhere in the ntp docs it says ntpd will not change the time if
>the offset is too large...
Yes. Here is the exact quote from the current man page for 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.
So either I need new glasses or else that part underlined above is just plain
wrong. Because even after my ntpd died several times, I was unable to find
-any- message telling me that ntpd had chosen suicide, let alone what the
reasons for that might have been. At least not in /var/log/messages.
>You can use ntpq to check the status of things ntp. There are lots of "neat"
>commands...
Yea. I know. But thank you.
Alas, that command/program isn't really all that informative if ntpd isn't
even running.
Regards,
rfg
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?52802.1559769936>