From owner-freebsd-questions@freebsd.org Wed Jun 5 21:25:46 2019 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 04DA415B973C for ; Wed, 5 Jun 2019 21:25:46 +0000 (UTC) (envelope-from rfg@tristatelogic.com) Received: from outgoing.tristatelogic.com (segfault.tristatelogic.com [69.62.255.118]) by mx1.freebsd.org (Postfix) with ESMTP id C8CF96DA44 for ; Wed, 5 Jun 2019 21:25:43 +0000 (UTC) (envelope-from rfg@tristatelogic.com) Received: from segfault-nmh-helo.tristatelogic.com (localhost [127.0.0.1]) by segfault.tristatelogic.com (Postfix) with ESMTP id A9C513AEFE for ; Wed, 5 Jun 2019 14:25:36 -0700 (PDT) From: "Ronald F. Guilmette" To: freebsd-questions@freebsd.org Subject: Re: ntpd configutration -- a small suggestion from the peanut gallery In-Reply-To: Date: Wed, 05 Jun 2019 14:25:36 -0700 Message-ID: <52802.1559769936@segfault.tristatelogic.com> X-Rspamd-Queue-Id: C8CF96DA44 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of rfg@tristatelogic.com designates 69.62.255.118 as permitted sender) smtp.mailfrom=rfg@tristatelogic.com X-Spamd-Result: default: False [-6.29 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-questions@freebsd.org]; TO_DN_NONE(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; DMARC_NA(0.00)[tristatelogic.com]; MX_GOOD(-0.01)[mx1.tristatelogic.com]; NEURAL_HAM_SHORT(-0.94)[-0.939,0]; IP_SCORE(-3.14)[ip: (-8.28), ipnet: 69.62.128.0/17(-4.14), asn: 14051(-3.23), country: US(-0.06)]; RCVD_NO_TLS_LAST(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:14051, ipnet:69.62.128.0/17, country:US]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Jun 2019 21:25:46 -0000 In message , 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