From owner-freebsd-questions@freebsd.org Sat Apr 27 19:29:33 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 407C4159A8D5 for ; Sat, 27 Apr 2019 19:29:33 +0000 (UTC) (envelope-from kremels@kreme.com) Received: from mail.covisp.net (mail.covisp.net [65.121.55.42]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B0DF56B7F6 for ; Sat, 27 Apr 2019 19:29:31 +0000 (UTC) (envelope-from kremels@kreme.com) From: "@lbutlr" Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: Re: Help with ntpd Date: Sat, 27 Apr 2019 13:29:21 -0600 References: <62834f37-f517-9807-9303-584cdacddc31@missouri.edu> To: RW via freebsd-questions In-Reply-To: <62834f37-f517-9807-9303-584cdacddc31@missouri.edu> Message-Id: X-Mailer: Apple Mail (2.3445.104.8) X-Rspamd-Queue-Id: B0DF56B7F6 X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of kremels@kreme.com designates 65.121.55.42 as permitted sender) smtp.mailfrom=kremels@kreme.com X-Spamd-Result: default: False [-1.10 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.83)[-0.829,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; MISSING_MIME_VERSION(2.00)[]; MIME_GOOD(-0.10)[text/plain]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DMARC_NA(0.00)[kreme.com]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-0.89)[-0.889,0]; IP_SCORE(-0.21)[ip: (-0.59), ipnet: 65.112.0.0/12(-0.30), asn: 209(-0.12), country: US(-0.06)]; TO_DN_ALL(0.00)[]; MX_GOOD(-0.01)[mail.covisp.net]; NEURAL_HAM_SHORT(-0.75)[-0.755,0]; RCVD_COUNT_ZERO(0.00)[0]; RCVD_IN_DNSWL_LOW(-0.10)[42.55.121.65.list.dnswl.org : 127.0.5.1]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:209, ipnet:65.112.0.0/12, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[]; FROM_EQ_ENVFROM(0.00)[] 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: Sat, 27 Apr 2019 19:29:33 -0000 > On 27 Apr 2019, at 11:30, Montgomery-Smith, Stephen = wrote: >=20 > For some reason, ntpd has stopped correcting the time on my FreeBSD > computer. After 12 hours, my clock has fallen back 4 hours! So it is > very serious. If the time offset it too high, ntpd will not change it. This might help: -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. -G, --force-step-once Step any initial offset correction.. Normally, ntpd steps the time if the time offset exceeds = the step threshold, which is 128 ms by default, and otherwise slews = the time. This option forces the initial offset correction to = be stepped, so the highest time accuracy can be achieved = quickly. However, this may also cause the time to be stepped back so = this option must not be used if applications requiring monotonic = time are running. See the tinker configuration file directive = for other options. > Every so often I correct the time with "ntpdate = 0.freebsd.pool.ntp.org", > but the lag starts right away after the update. If you do NOT correct the time does the lag continue to grow? How = quickly? What is your timezone set to? Have you told your system to be = on UTC or local time? Is your BIOS set to UTC or the local time? --=20 Dinner will be ready when the smoke alarm goes off.