From owner-freebsd-hackers@freebsd.org Tue Jan 5 15:41:30 2021
Return-Path: <owner-freebsd-hackers@freebsd.org>
Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
by mailman.nyi.freebsd.org (Postfix) with ESMTP id CFE184C019A
for <freebsd-hackers@mailman.nyi.freebsd.org>;
Tue, 5 Jan 2021 15:41:30 +0000 (UTC)
(envelope-from freebsd-rwg@gndrsh.dnsmgr.net)
Received: from gndrsh.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140])
(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
(Client did not present a certificate)
by mx1.freebsd.org (Postfix) with ESMTPS id 4D9Gtx5XMrz4crq
for <freebsd-hackers@freebsd.org>; Tue, 5 Jan 2021 15:41:29 +0000 (UTC)
(envelope-from freebsd-rwg@gndrsh.dnsmgr.net)
Received: from gndrsh.dnsmgr.net (localhost [127.0.0.1])
by gndrsh.dnsmgr.net (8.13.3/8.13.3) with ESMTP id 105FfQI0008108;
Tue, 5 Jan 2021 07:41:26 -0800 (PST)
(envelope-from freebsd-rwg@gndrsh.dnsmgr.net)
Received: (from freebsd-rwg@localhost)
by gndrsh.dnsmgr.net (8.13.3/8.13.3/Submit) id 105FfQq6008107;
Tue, 5 Jan 2021 07:41:26 -0800 (PST) (envelope-from freebsd-rwg)
From: "Rodney W. Grimes" <freebsd-rwg@gndrsh.dnsmgr.net>
Message-Id: <202101051541.105FfQq6008107@gndrsh.dnsmgr.net>
Subject: Re: How does the time zone info get updated?
In-Reply-To: <20210105075109.A412C40605C@ip-64-139-1-69.sjc.megapath.net>
To: Hal Murray <hmurray@megapathdsl.net>
Date: Tue, 5 Jan 2021 07:41:25 -0800 (PST)
CC: freebsd-hackers@freebsd.org
X-Mailer: ELM [version 2.4ME+ PL121h (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=US-ASCII
X-Rspamd-Queue-Id: 4D9Gtx5XMrz4crq
X-Spamd-Bar: -
Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none;
spf=none (mx1.freebsd.org: domain of freebsd-rwg@gndrsh.dnsmgr.net has no SPF
policy when checking 69.59.192.140)
smtp.mailfrom=freebsd-rwg@gndrsh.dnsmgr.net
X-Spamd-Result: default: False [-1.10 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[];
ARC_NA(0.00)[]; MID_RHS_MATCH_FROM(0.00)[];
FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[];
NEURAL_HAM_MEDIUM(-1.00)[-1.000];
NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain];
RCVD_TLS_LAST(0.00)[];
RBL_DBL_DONT_QUERY_IPS(0.00)[69.59.192.140:from];
AUTH_NA(1.00)[]; DMARC_NA(0.00)[dnsmgr.net];
SPAMHAUS_ZRD(0.00)[69.59.192.140:from:127.0.2.255];
TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_SHORT(-1.00)[-1.000];
RCPT_COUNT_TWO(0.00)[2]; R_SPF_NA(0.00)[no SPF record];
FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[];
MIME_TRACE(0.00)[0:+]; RCVD_COUNT_TWO(0.00)[2];
ASN(0.00)[asn:13868, ipnet:69.59.192.0/19, country:US];
MAILMAN_DEST(0.00)[freebsd-hackers]
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.34
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
<freebsd-hackers.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-hackers>,
<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers/>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Jan 2021 15:41:30 -0000
>
> It gets distributed with the base packages, but I haven't figured out how to
> keep it up to date.
>
> The info is distributed via IANA.
> https://www.iana.org/time-zones
>
> It gets updated several times a year. There were 6 during 2020. When is
> unpredictable, often shortly after some government passes a law to change
> something with short notice.
>
> I'd expect there to be some mechanism to track the updates but I haven't found
> it.
>
> The tz database includes the leap-seconds.list file. That gets updated every
> 6 months. I'd like to get whatever FreeBSD does for time zones to include
> that file so ntpd can use it without having to be concerned with keeping it up
> to date. That only works if the zone info is kept up to date.
This only addresses the leap-seconds file, not the whole zoneinfo data:
/etc/periodic/daily/480.leapfile-ntp calls "service ntpd onefetch",
which is /etc/rc.d/ntpd, the onefetch command attempts to update
the leap-second file.
This works great if you have https support avaliable via the ca_root_nss
port, if you do not then you can fix this to fetch via http by overriding
ntp_leapfile_sources in /etc/rc.conf like so:
ntp_leapfile_sources="http://www.ietf.org/timezones/data/leap-seconds.list"
^ remove s here
This is the only file you need to keep up to date to keep ntpd happy.
--
Rod Grimes rgrimes@freebsd.org