From nobody Sun Jul 07 19:07:02 2024
X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
	by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4WHGw05Q4hz5QJqh
	for <freebsd-arm@mlmmj.nyi.freebsd.org>; Sun, 07 Jul 2024 19:07:12 +0000 (UTC)
	(envelope-from saper@saper.info)
Received: from q.saper.info (q.saper.info [IPv6:2605:2700:0:2:a800:ff:fec7:5c61])
	(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 ECDSA (P-384) client-digest SHA384)
	(Client CN "q.saper.info", Issuer "R3" (verified OK))
	by mx1.freebsd.org (Postfix) with ESMTPS id 4WHGw01tgTz45Dl
	for <freebsd-arm@freebsd.org>; Sun,  7 Jul 2024 19:07:12 +0000 (UTC)
	(envelope-from saper@saper.info)
Authentication-Results: mx1.freebsd.org;
	none
Received: from q.saper.info (localhost [127.0.0.1])
	by q.saper.info (8.18.1/8.18.1) with ESMTPS id 467J72SE081102
	(version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO);
	Sun, 7 Jul 2024 19:07:03 GMT
	(envelope-from saper@saper.info)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=saper.info; s=Sep2014;
	t=1720379223; bh=nNGbkhyiBynaAPdiAsTmLU11S9+kGGIFdtE6I3UQRvQ=;
	h=Date:From:To:cc:Subject:In-Reply-To:References;
	b=QrVKnRgOMeYj0fBlBMCFH5twOBKoQ5aBAJSUR6uVafHyLpqrEY2am8B/blr1DByKu
	 BFHSr8LAe9uIRT3HpQFf0y11J1aqeeQEAIEGid1ywo507si5nAZBrXr6lZ9AOkLQ9z
	 7qyvS1uucMcZemsnn9hR02XGDCvk2iMeJXz3ga3g=
Received: from localhost (saper@localhost)
	by q.saper.info (8.18.1/8.18.1/Submit) with ESMTP id 467J72xr081099;
	Sun, 7 Jul 2024 19:07:02 GMT
	(envelope-from saper@saper.info)
X-Authentication-Warning: q.saper.info: saper owned process doing -bs
Date: Sun, 7 Jul 2024 19:07:02 +0000
From: Marcin Cieslak <saper@saper.info>
To: Ronald Klop <ronald-lists@klop.ws>
cc: bob prohaska <fbsd@www.zefox.net>, freebsd-arm@freebsd.org
Subject: Re: ntpd vs ntpdate with no hardware clock
In-Reply-To: <454282477.15929.1720372600841@localhost>
Message-ID: <1643prpr-11o6-9s9p-0r34-ns09136o5sqr@fncre.vasb>
References: <454282477.15929.1720372600841@localhost>
List-Id: Porting FreeBSD to ARM processors <freebsd-arm.freebsd.org>
List-Archive: https://lists.freebsd.org/archives/freebsd-arm
List-Help: <mailto:freebsd-arm+help@freebsd.org>
List-Post: <mailto:freebsd-arm@freebsd.org>
List-Subscribe: <mailto:freebsd-arm+subscribe@freebsd.org>
List-Unsubscribe: <mailto:freebsd-arm+unsubscribe@freebsd.org>
Sender: owner-freebsd-arm@FreeBSD.org
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
X-Spamd-Bar: ----
X-Rspamd-Pre-Result: action=no action;
	module=replies;
	Message is reply to one we originated
X-Spamd-Result: default: False [-4.00 / 15.00];
	REPLY(-4.00)[];
	ASN(0.00)[asn:47066, ipnet:2605:2700::/32, country:US]
X-Rspamd-Queue-Id: 4WHGw01tgTz45Dl

On Sun, 7 Jul 2024, Ronald Klop wrote:

> I created fakertc for my rpi4. 
> https://www.freshports.org/sysutils/fakertc/
>
> Saves the time on shutdown and sets it back early at boot.
>
> Plus I use ntpdate together with ntpd. Works fine.

I have question here:

Rrecently I have removed an RTC battery
from my amd64 system and it turned out
that ntpd couldn't do anything to set the time
because the local DNS resolver failed
(I presume it was dnssec failure).

What is the most elegant solution to
cope with such a race condition?
(DNS needs time, setting time needs DNS)

Marcin