From owner-freebsd-arm@freebsd.org Tue May 4 15:42:25 2021 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id A330D6363D5 for ; Tue, 4 May 2021 15:42:25 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "www.zefox.com", Issuer "www.zefox.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4FZPH45C7lz3QnH; Tue, 4 May 2021 15:42:24 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.16.1/8.15.2) with ESMTPS id 144FgJrM047631 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Tue, 4 May 2021 08:42:20 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.16.1/8.15.2/Submit) id 144FgJCe047630; Tue, 4 May 2021 08:42:19 -0700 (PDT) (envelope-from fbsd) Date: Tue, 4 May 2021 08:42:19 -0700 From: bob prohaska To: Ian Lepore Cc: freebsd-arm@freebsd.org, bob prohaska Subject: Re: Timezone problems on -current Message-ID: <20210504154219.GA47280@www.zefox.net> References: <20210503153442.GB37236@www.zefox.net> <20210504015222.GE37236@www.zefox.net> <8e4843ce80e9bc005da5ca42d43e0bc34ce2c6ff.camel@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8e4843ce80e9bc005da5ca42d43e0bc34ce2c6ff.camel@freebsd.org> X-Rspamd-Queue-Id: 4FZPH45C7lz3QnH X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of fbsd@www.zefox.net has no SPF policy when checking 50.1.20.27) smtp.mailfrom=fbsd@www.zefox.net X-Spamd-Result: default: False [-1.10 / 15.00]; RCVD_TLS_ALL(0.00)[]; ARC_NA(0.00)[]; WWW_DOT_DOMAIN(0.50)[]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[zefox.net]; RBL_DBL_DONT_QUERY_IPS(0.00)[50.1.20.27:from]; AUTH_NA(1.00)[]; SPAMHAUS_ZRD(0.00)[50.1.20.27:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_SHORT(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_SPF_NA(0.00)[no SPF record]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:7065, ipnet:50.1.16.0/20, country:US]; RCVD_COUNT_TWO(0.00)[2]; MAILMAN_DEST(0.00)[freebsd-arm]; MID_RHS_WWW(0.50)[] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Porting FreeBSD to ARM processors List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 May 2021 15:42:25 -0000 On Tue, May 04, 2021 at 08:42:14AM -0600, Ian Lepore wrote: > On Mon, 2021-05-03 at 18:52 -0700, bob prohaska wrote: > > > > Up to now I've used only the line > > ntpdate_enable="YES" > > and it's been enough to keep the clock sane. On the last reboot > > it appears ntpdate either didn't run or failed silently. The most > > You don't need to be running ntpdate at all. ntpd_sync_on_start gives > you the same effect... it allows ntpd to step the clock any required > amount, one time at startup. It's useful for systems that don't have a > battery-backed clock. > It seems clear that ntpd_sync_on_start is a better choice than ntpdate. Clock drift on the Pi seems fairly slow, a couple seconds a month, but staying right on can't hurt and doesn't cost much. > I like to set kern.timecounter.stepwarnings=1 in /etc/sysctl.conf so I > have a record in syslog of when ntpd steps the clock. Most of my trouble seems to have been caused by timesetting not running at startup and me not noticing promptly. A combination of ntpd_sync_on_start and a -g flag will set the clock and make a fuss in the logfiles if time drifts too far off. Is there a way to make a fuss if ntpd fails to start in the first place or quits in mid-flight? Thanks for writing! bob prohaska