From nobody Sun Jul 07 16:28:47 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 4WHCPV06z6z5Q2bf for ; Sun, 07 Jul 2024 16:29:02 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-pg1-x535.google.com (mail-pg1-x535.google.com [IPv6:2607:f8b0:4864:20::535]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4WHCPT2LrRz4gPB for ; Sun, 7 Jul 2024 16:29:01 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-pg1-x535.google.com with SMTP id 41be03b00d2f7-76cb5b6b3e4so432186a12.1 for ; Sun, 07 Jul 2024 09:29:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20230601.gappssmtp.com; s=20230601; t=1720369739; x=1720974539; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=K/AY43GebHxkFghw5yZ2iWrYwsYX91oJ5H0a6/Vv7hw=; b=ghBmkYwEBfYbnhY8Fjw3GGovVy+VWKI62nK14lciCXq8wb4G9g2mclFRWcJrKeqKNK cHNRzGk4A8bryFTY06qdg7fO41a0QTb9yze48RxII2ff4VC7P949fdj+WHfxmVEQaIg8 /Nre/zBn+oEUk56rI7DhqzjLV8gIBK7jgsTYDhqjo3RYHYbR+JUywB+7u1ETG1LicsTc BMNPfNvh3THhklL/t7Jiy7/iTEIMWxCfEYPcsVD1vIDL0Gydh3KFjy4II5OacoM4oNCC 5W3evHRZxAcwG1/S1MhfYfRSUoThdoljvT3/HPHViia1Bwc5yLvs8zmzzw+e8ZpgS/eR D8dA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1720369739; x=1720974539; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=K/AY43GebHxkFghw5yZ2iWrYwsYX91oJ5H0a6/Vv7hw=; b=UAyk8y8BIKnVGwVUTzedwBKOVv5Xpsx2YcC8hNl1RYj/CGrZojVTk69Td+CBhMo2Kn MlmJB7tVSeTbbbNjdsfgM7ABha+jj5OjJutXo+7P+UkpKdK1uTvMDi2sQTBz9pmp3HVR hErp4YcjY5GXIovFZLpCRLDnlxlMIBjzPcXhYVrXCmbcW5pnJW62X+5j8kfQnjg/KWVE yfCSsJGQR80ZADWjcL8gQijJah9nH7THLoSxTtb84jIh66DBjKWKa6SDcNB5aXO5UIiY qizLLcQPOIzc8jiQgvbzP1Klh/PaiZb8zRT2aXcJeGGdjlEPWkBi1fLmTF4MGvU0JWob DMjg== X-Forwarded-Encrypted: i=1; AJvYcCXbXJWd5hmZA6nHosShcooycITbhIJieKeDuJvfgGfKA//JwGN+WWBaQZXR/CpkQJ7T2qSoQ+4/DC1v9RIa7EeH10QJ1dxlhQ== X-Gm-Message-State: AOJu0Yx34AJAmgIRhd7ZnrUPFexrkn2QAFHlKF5ZgDNKHhXnIdFG26sc z05nzfFcvnXS32g0fZpZkxkgav3sNNuQnHtLirjXuYvpMadzGZxtzA3C0SbPnq6gyVmAEtovTxv 9wHbSLrdamktAnQAE7P2CWRCWaOPaMixm94Y6ig== X-Google-Smtp-Source: AGHT+IGvMGAttKZV7rny5J+1tA5sSKQCINkl/LrBSFniyUCxtNVz7ENvG0zoSgiEaB6AVvSENLRInoyJYZGYVMG0J7A= X-Received: by 2002:a17:90a:6588:b0:2c9:649c:5e08 with SMTP id 98e67ed59e1d1-2c99c6ac810mr5911515a91.15.1720369739425; Sun, 07 Jul 2024 09:28:59 -0700 (PDT) List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@FreeBSD.org MIME-Version: 1.0 References: <663B8441-A84B-481A-95D6-D22EDC4E66A3@yahoo.com> In-Reply-To: <663B8441-A84B-481A-95D6-D22EDC4E66A3@yahoo.com> From: Warner Losh Date: Sun, 7 Jul 2024 10:28:47 -0600 Message-ID: Subject: Re: ntpd vs ntpdate with no hardware clock To: Mark Millard Cc: bob prohaska , "freebsd-arm@freebsd.org" Content-Type: multipart/alternative; boundary="000000000000338a9f061caacbaf" 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:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Queue-Id: 4WHCPT2LrRz4gPB --000000000000338a9f061caacbaf Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sun, Jul 7, 2024, 10:24=E2=80=AFAM Mark Millard wrot= e: > On Jul 7, 2024, at 09:01, bob prohaska wrote: > > > Just tried using ntpd with a fresh 14.1 installation on a Pi4. > > Near as I can tell, ntpd reports a failure due to the clock > > being off by too much, even if it's set manually to within > > a minute before reboot. Probably that's caused by the lack > > of a hardware clock on the Pi4, linux has a bodge called > > fake-hwclock. Is there an equivalent workaround for FreeBSD? > > > > In the meantime ntpdate seems to work, though deprecated > > FYI: my /etc/rc.conf for media sometimes used on such > hardware has: > > ntpd_enable=3D"YES" > ntpd_sync_on_start=3D"YES" > ntpd_user=3D"root" > > "man 5 rc.conf" reports about ntpd_sync_on_start : > > ntpd_sync_on_start > (bool) If set to =E2=80=9CYES=E2=80=9D, ntpd(8) is run w= ith the -g flag, > which syncs the system's clock on startup. See ntpd(8) > for > more information regarding the -g option. This is a > preferred alternative to using ntpdate(8) or specifying > the > ntpdate_enable variable. > Maybe it is -g now. This is better advice than what i said.. Warner > =3D=3D=3D > Mark Millard > marklmi at yahoo.com > > > --000000000000338a9f061caacbaf Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Sun, Jul 7, 2024, 10:24=E2=80=AFAM Mark Millard <= ;marklmi@yahoo.com> wrote:
<= /div>
On Jul 7, 2024, at 09:01, bob prohaska = <fbsd@www.zefox.net> wrote:

> Just tried using ntpd with a fresh 14.1 installation on a Pi4.
> Near as I can tell, ntpd reports a failure due to the clock
> being off by too much, even if it's set manually to within
> a minute before reboot. Probably that's caused by the lack
> of a hardware clock on the Pi4, linux has a bodge called
> fake-hwclock. Is there an equivalent workaround for FreeBSD?
>
> In the meantime ntpdate seems to work, though deprecated

FYI: my /etc/rc.conf for media sometimes used on such
hardware has:

ntpd_enable=3D"YES"
ntpd_sync_on_start=3D"YES"
ntpd_user=3D"root"

"man 5 rc.conf" reports about ntpd_sync_on_start :

=C2=A0 =C2=A0 =C2=A0ntpd_sync_on_start
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0(bool) If set= to =E2=80=9CYES=E2=80=9D, ntpd(8) is run with the -g flag,
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0which syncs t= he system's clock on startup.=C2=A0 See ntpd(8) for
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0more informat= ion regarding the -g option.=C2=A0 This is a
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0preferred alt= ernative to using ntpdate(8) or specifying the
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0ntpdate_enabl= e variable.

Maybe it is -g now. This is better advice than what i said..

Warner


=3D=3D=3D
Mark Millard
marklmi at yahoo.com


--000000000000338a9f061caacbaf--