From nobody Sun Jul 07 16:16:34 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 4WHC7N3wVHz5Q1Rq for ; Sun, 07 Jul 2024 16:16:48 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-pl1-x62a.google.com (mail-pl1-x62a.google.com [IPv6:2607:f8b0:4864:20::62a]) (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 4WHC7N21Qhz4dYt for ; Sun, 7 Jul 2024 16:16:48 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-pl1-x62a.google.com with SMTP id d9443c01a7336-1fb4a332622so8740845ad.2 for ; Sun, 07 Jul 2024 09:16:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20230601.gappssmtp.com; s=20230601; t=1720369007; x=1720973807; 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=0omUVjcZaVBb/DSu4r3ATpCTO5unduL6YnnSpR20HhQ=; b=QZTUea5f0IEUggCw7HQGFPCONkDo/dq95ywu+eYxeVZIWeLLMy9yUjmeYXIeyJLJ/4 +KKW1iN8VcMA1hSl6sBPtfifb3MdIABYvB7XsjgGjBZuyEHgVwud0kHDJkmrYSCqQCWL cB1bxxt/inClE++ZT5uvSBh9BSZ9zF5VCwuNtQkUnDQGsf0syTRqlfoY+lasPVFFQP8G ztSkkJhAsiDpXP46qqqaaSc4ga1g8bDOaF1cSwmcOcurX7jGWtjNwEt181iVVP+JudTf d8B56IyMrMgyBcX3ZUAIEDvCrajSlkHS78QirDSPrlMJs+t9C683e3PpYoxelKaMWN7b IuwA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1720369007; x=1720973807; 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=0omUVjcZaVBb/DSu4r3ATpCTO5unduL6YnnSpR20HhQ=; b=Dk+QCxVCZdVcCcN0pvL3JHSJKv3NMELrDcQT4DtsbxQm7o/Dq6Wyts1fG7kAtf1COq RO2e4CoCYgRV79k0Suxz95x8LxlKOI54povB37iFvy6JPraa6WfOSp4EuQYS4+WrHj8R XcJYenHK9Q/ESF//DPLciJjtf1ZmpkVckuMPQUX1hlhBqYRYF64Cbz0n4HZ1fo+pbLJ+ FkxpQS6Drp5GhrZ5vishdyEvjLHNrjVTyCtct8JjMmg9Rudzc6d0uh2cIrDMncIEoaTj ZawgS2hob7ff/qMuecqqCKnUA+edGsdyMHtPIjF2PqmYeGgjksna3V9T59kfYc6GcQj3 A28A== X-Gm-Message-State: AOJu0YzMuaAXKsDVr3YBjpG3qjp0TaHMLswfoeXNl49bM0DHsuYu47k3 Yj8Kk66AHfj/+uPiKz/OmlRMC4FQVK1M9Ox98uJNjKpC9UkXqoIt8rO4lDWesyZ2hML0XKb0Twd ltg4zY/pyRb+mhY2yeV9G8CbX5C4Pu4TXbEsZDiFbdA2KUq0r X-Google-Smtp-Source: AGHT+IEiqDERj/BuBYEmfQ5Pb187eUnD7v5i1MpF6fMuinbE6XNSPZyy/y9WyuYlBbw9YkRqNBtTAGXEVLg6j3YF+oQ= X-Received: by 2002:a17:90a:898f:b0:2c9:3340:621d with SMTP id 98e67ed59e1d1-2c99c86bd51mr5505531a91.37.1720369006599; Sun, 07 Jul 2024 09:16:46 -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: In-Reply-To: From: Warner Losh Date: Sun, 7 Jul 2024 10:16:34 -0600 Message-ID: Subject: Re: ntpd vs ntpdate with no hardware clock To: bob prohaska Cc: "freebsd-arm@freebsd.org" Content-Type: multipart/alternative; boundary="0000000000008585a9061caa9f60" 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: 4WHC7N21Qhz4dYt --0000000000008585a9061caa9f60 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Try -q on ntpd. It will step system time, but only once. FreeBSD will set the time to the last modification of /. At least for UFS... I'm guessing this is why it was within a minute.... and is FreeBSD's psuedo equivalent. Warner. On Sun, Jul 7, 2024, 10:01=E2=80=AFAM bob prohaska wro= te: > 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 > > Thanks for reading, > > bob prohaska > > > --0000000000008585a9061caa9f60 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Try -q on ntpd. It will step system time, but only once.<= div dir=3D"auto">
FreeBSD will set the time to t= he last modification of /. At least for UFS... I'm guessing this is why= it was within a minute.... and is FreeBSD's psuedo equivalent.=C2=A0

Warner.

On Sun, Jul = 7, 2024, 10:01=E2=80=AFAM 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

Thanks for reading,

bob prohaska


--0000000000008585a9061caa9f60--