Date: Tue, 5 Jan 2021 07:41:25 -0800 (PST) From: "Rodney W. Grimes" <freebsd-rwg@gndrsh.dnsmgr.net> To: Hal Murray <hmurray@megapathdsl.net> Cc: freebsd-hackers@freebsd.org Subject: Re: How does the time zone info get updated? Message-ID: <202101051541.105FfQq6008107@gndrsh.dnsmgr.net> In-Reply-To: <20210105075109.A412C40605C@ip-64-139-1-69.sjc.megapath.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> > 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?202101051541.105FfQq6008107>