From nobody Tue Nov 28 11:33:48 2023 X-Original-To: questions@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 4SfgMW5zdvz52xDc for ; Tue, 28 Nov 2023 11:33:59 +0000 (UTC) (envelope-from listac@nebelschwaden.de) Received: from mail.worldserver.net (mail.worldserver.net [217.13.200.36]) (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 "*.worldserver.net", Issuer "EuropeanSSL Server CA 2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4SfgMV222Gz3J2J for ; Tue, 28 Nov 2023 11:33:58 +0000 (UTC) (envelope-from listac@nebelschwaden.de) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=nebelschwaden.de header.s=1687803001 header.b=BMz9GRuC; spf=pass (mx1.freebsd.org: domain of listac@nebelschwaden.de designates 217.13.200.36 as permitted sender) smtp.mailfrom=listac@nebelschwaden.de; dmarc=none Received: from postpony.nebelschwaden.de (v22018114346177759.hotsrv.de [194.55.14.20]) (Authenticated sender: sendmail@nebelschwaden.de) by mail.worldserver.net (Postfix) with ESMTPSA id AB7751E0B19 for ; Tue, 28 Nov 2023 12:33:50 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nebelschwaden.de; s=1687803001; t=1701171230; bh=A2rQfUJnGrJhE++BKvfTe0gTn7YOnXsCUVMnbKoZk/4=; h=Date:Reply-To:Subject:To:References:From:In-Reply-To:From; b=BMz9GRuCGQpwxKNAYTgyHTjMlqOwy/g2aI5goraZotIQ9amAwBIufwSfq4z+H3MYK oXeSvXLkEnYGAEgMkWH1j0ngbfGgGvxTLIKDaQdBB/NN715jmZQ3LOtP8ELAI5WRqw iObxjBc8nxV1ik0nZ8+WxMwT72BDTgcFbbDH3Xh7jT58YarQjuPscu+Va/lCDDzJsQ BQdYRoXWt50O1DFUPyGxCoOhO9hzwtfqq35QngJ7GX3Stos0W0F573OU1k+l8WqRV3 CN+BSb7r6cYLCy/QKQBXlykw8uuwsGg1PvbPJ2XMBwbs+JCfAlSChY/AzZUM3c3BXJ INWUbA8phmM5w== Received: from [172.16.37.5] (kaperfahrt.nebelschwaden.de [172.16.37.5]) by postpony.nebelschwaden.de (Postfix) with ESMTP id B2390117CA6 for ; Tue, 28 Nov 2023 12:33:48 +0100 (CET) Message-ID: <5541217f-f86e-4308-a4b0-5728472e2102@nebelschwaden.de> Date: Tue, 28 Nov 2023 12:33:48 +0100 List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Reply-To: listac@nebelschwaden.de Subject: Re: NTPD leap second file To: questions@freebsd.org References: <1749db2d-757f-4fc1-ba5c-f1b05fbb40f3@cloudzeeland.nl> <20231128102806.1bd6ef76a878e98dbb11bf2c@sohara.org> Content-Language: en-US From: Ede Wolf In-Reply-To: <20231128102806.1bd6ef76a878e98dbb11bf2c@sohara.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spamd-Result: default: False [-2.57 / 15.00]; NEURAL_HAM_MEDIUM(-0.99)[-0.989]; NEURAL_HAM_SHORT(-0.91)[-0.913]; R_DKIM_ALLOW(-0.20)[nebelschwaden.de:s=1687803001]; R_SPF_ALLOW(-0.20)[+ip4:217.13.200.0/24]; RCVD_IN_DNSWL_LOW(-0.10)[217.13.200.36:from]; MIME_GOOD(-0.10)[text/plain]; NEURAL_HAM_LONG(-0.08)[-0.079]; XM_UA_NO_VERSION(0.01)[]; RCPT_COUNT_ONE(0.00)[1]; ARC_NA(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[questions@freebsd.org]; DMARC_NA(0.00)[nebelschwaden.de]; TO_MATCH_ENVRCPT_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; HAS_REPLYTO(0.00)[listac@nebelschwaden.de]; MID_RHS_MATCH_FROM(0.00)[]; ASN(0.00)[asn:15657, ipnet:217.13.192.0/20, country:DE]; TO_DN_NONE(0.00)[]; REPLYTO_ADDR_EQ_FROM(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; MLMMJ_DEST(0.00)[questions@freebsd.org]; DKIM_TRACE(0.00)[nebelschwaden.de:+]; MIME_TRACE(0.00)[0:+]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-Rspamd-Queue-Id: 4SfgMV222Gz3J2J X-Spamd-Bar: -- Am 28.11.23 um 11:28 schrieb Steve O'Hara-Smith: > On Tue, 28 Nov 2023 10:33:45 +0100 > Jos Chrispijn wrote: > >> Recently I noticed this: >> >> fetch: https://www.ietf.org/timezones/data/leap-seconds.list: Not Found > > Where did you notice it ? > >> Looks to be an NTPD leap second file, which isn't supported by ietf.org >> anymore. > > I found more than I ever wanted to know about leap second files > here: > > > > It has many alternative links, it's far from clear that they have > the same data. > > It seems the one I currently have in /var/db expires on 20th dec - > I'll keep an eye out for what happens. > Now, the leap seconds are, AFAIK, internationally coordinated by ITU. Still. So, unless the server you are fetchting from is outdated itself, they all should have the same data. It is an ascii file and it tells you inside, when it will be expiring so you can easily check it being recent. Other than that, if yours is expired, you'll see a message being logged during start up of ntpd, that's probably about it. crystal ball: If a leap second is inserted - with your list being expired - you may have that offset, and your ntpd will smoothly catch up with it rather quickly. Should only happen at the very end of the year, if at all. I am not aware of the next planned leap second. But that does not mean anything, of course. Oh, and, it seems, from 2035 on, leap seconds may be gone alltogether. https://theconversation.com/its-time-out-for-leap-seconds-an-expert-explains-why-the-tiny-clock-adjustments-will-be-paused-from-2035-194922 https://earthsky.org/human-world/leap-second-june-30-december-31-why-need-controversy/ If somebody knows better, please let us know.