From owner-freebsd-questions@freebsd.org Wed Jun 5 19:42:06 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 21B3F15B7560 for ; Wed, 5 Jun 2019 19:42:06 +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 E080A6A4FC for ; Wed, 5 Jun 2019 19:42:04 +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 015063AEFE for ; Wed, 5 Jun 2019 12:42:03 -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: <58688a77362d7caad70df844d5077d0916f7f944.camel@smormegpa.no> Date: Wed, 05 Jun 2019 12:42:02 -0700 Message-ID: <52339.1559763722@segfault.tristatelogic.com> X-Rspamd-Queue-Id: E080A6A4FC 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.32 / 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)[cached: mx1.tristatelogic.com]; NEURAL_HAM_SHORT(-0.98)[-0.980,0]; IP_SCORE(-3.13)[ip: (-8.24), ipnet: 69.62.128.0/17(-4.12), asn: 14051(-3.21), 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 19:42:06 -0000 In message <58688a77362d7caad70df844d5077d0916f7f944.camel@smormegpa.no>, Matthias Oestreicher wrote: >> Did I just miss those ntpd death messages somehow? >Sorry, I've never seen ntpd exit due to too big offset and I don't know how that would >show in /var/log/messages. It would appear that, most probably, nobody knows what the ntpd suicide log messages look like, because it doesn't actually produce any (contrary to what the man page says). >Anyway, even if it seems to work now, I'd check if your time is based on localtime or >GMT. It's recommended to use GMT, I never use localtime personally. For me, I prefer local time. When I type "date" I don't really give a flying fig what time it is in London. I'm in California. >In your original question you said:"off by several hours"... I don't think I said anything like that, but anyway,. yes, it is possible that my BIOS clock was set way way off. (I actually think that it was set quite close to actual local time, but I could be wrong about that.) >and that's usually caused by >having FreeBSD configured to use localtime, while the hardware clock in the BIOS is set >to GMT (or maybe the otherway around). Yes. Most likely the other way around in my case. >This happend to me once, when I accidentally >chose localtime during install, while I had BIOS clock set to GMT. I was totally >confused and wondered where that offset came from, until I got the hint to remove >/etc/wall_cmos_clock on the forums. > >That said, check if the file /etc/wall_cmos_clock exists and if, remove it (it's an >empty file). Well, *that* is bloody confusing. I thought that someone here just recommended to me that I make suere that I *do* have this file... *not* that I don't have it. >Normally, neither the -g option nor sync_on_start should be needed, if the hardware >clock in your computer's BIOS is correctly set to GMT. Doesn't hurt to use them, but if >ntpd does not work without, I'd check the clock. See above and my various other messages. I need to keep the BIOS clock set to local time for reasons having nothing to do with FreeBSD. Anyway, no worries. I'm a happy camper now. Ntpd is running and all is well with the world. Regards, rfg