From owner-freebsd-hackers@freebsd.org Tue Jan 5 20:36:45 2021 Return-Path: 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 7556F4C9CF9 for ; Tue, 5 Jan 2021 20:36:45 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-qk1-x735.google.com (mail-qk1-x735.google.com [IPv6:2607:f8b0:4864:20::735]) (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 "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4D9PRd2Lsmz3J1D for ; Tue, 5 Jan 2021 20:36:45 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-qk1-x735.google.com with SMTP id w79so656136qkb.5 for ; Tue, 05 Jan 2021 12:36:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=HjY8fibpXVeFccScUfziSxCtSJyHEtCy6+imaQCq2Ko=; b=DkyvQUmoP9qFateiPpLFtRWSAJsa8dY3wRPYFpFSOs2Kod1OfBXr0fhzfu2oohCbkb MSOgj3roUt3RARpvgwknesmzolQ3a/qXsUnAZn2BzpfJPMDSzMjxqqAuclj+WkE+0Y8z 2OzkpkG+UKjd9WpBe2HxrilBU1TEymGBHl+lop+ped9hW0T5XQ0Gulk57TdYY99aBpuf CUaHfmsO8vqSJ0spbXiiFdsYebTo9ub8uHfkQ4b9e7darl2w578+c8jW9wRkYNyv1ytj JQjQYuG292IA+6/2aP3hko4ZRvHzvUXb+DNS7lfh/UX1vXG9VWE/lP0acXA1HEf5fNk9 JGEw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=HjY8fibpXVeFccScUfziSxCtSJyHEtCy6+imaQCq2Ko=; b=kKy4iNvZBa1T9Y4EehbwxwR97dmoDy3u1FSjMV3dy1YH8Y+d/XkDBfWgJckQ5th+ZO TPokVIUGGksb2kWGDsByG2/3q+NC2Yvp8dhhxI+4p8Ldh1vFVgGeVhSlm1p9CaPUSEfU G1VCWzRRJ8ek4Nqn8xQYk+hEHT82WqOO4W+aXZhJBRva6u8V9CzkG+xEIG9XB7HWWwFh ceeu+WArn9EDTCz/NvQrOzZ/uifQO/qPDbw4sYIzmGt+0F8F1j5oIWjFXZnINabM0jgj 09FLxFwPSyBdV0ugwkfp/Vyq4+LdKgorpKseAdzdd2lwZKcPbEKKqnvQB1hx1Ypm3Agw PsqQ== X-Gm-Message-State: AOAM532OIVIf9FTSEfb/JovoIN0U3NEIT0yDN9Khr25Q9kDGN4+kJbpC TaKeagBDyXsFIplW0ooZSHvmMMG83o6/7KNl8dj2iquO98X6qQ== X-Google-Smtp-Source: ABdhPJx9pNReLAFpbQEg3/tf8TmpVhAxCehphUXxMOgpoDmmI5ltbO3QZNgKyKL5PcKZ0LQYZBOjBouDnPRKnArmKLQ= X-Received: by 2002:a37:8505:: with SMTP id h5mr1342833qkd.44.1609879004278; Tue, 05 Jan 2021 12:36:44 -0800 (PST) MIME-Version: 1.0 References: <20210105075109.A412C40605C@ip-64-139-1-69.sjc.megapath.net> <4e6721bc-e593-76b6-90f8-03d96486dc28@freebsd.org> <47c37f75-e082-7a34-7eb6-3ee2a4ade395@freebsd.org> In-Reply-To: <47c37f75-e082-7a34-7eb6-3ee2a4ade395@freebsd.org> From: Warner Losh Date: Tue, 5 Jan 2021 13:36:33 -0700 Message-ID: Subject: Re: How does the time zone info get updated? To: Stefan Esser Cc: FreeBSD Hackers , Hal Murray X-Rspamd-Queue-Id: 4D9PRd2Lsmz3J1D X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.34 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jan 2021 20:36:45 -0000 On Tue, Jan 5, 2021 at 12:51 PM Stefan Esser wrote: > Am 05.01.21 um 16:49 schrieb Warner Losh: > > > > > > On Tue, Jan 5, 2021, 4:24 AM Stefan Esser > > wrote: > > > > Am 05.01.21 um 08:51 schrieb Hal Murray:> 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. > > > > We have recently moved the calendar files out of -CURRENT and into a > > port, and I could imagine providing the timezone files in the same > > way (without removal from base, but from there only used as a > fall-back > > if the port supplied files are not available). > > > > That way -STABLE users could update the definitions with base, but if > > you strictly follow a release, you could install the port and > decouple > > timezone file updates from base updates ... > > > > I'd be willing to support this change and maintain the data files, > but > > I can imagine that the current maintainer of those files in base > might > > want to do it himself. > > > > > > The calendar files aren't what he's talking about. > > Yes, I'm very well aware of that fact. > > > These are the timezone files he's asking about. Those get updated very > > shortly after upstream releases. > > Yes, and they are not considered critical security fixes and thus > are not available as patches for those that install binary releases. > > By providing the timezone files by a port/package in the same way > as the calendar data files (and preferring them if present), they > could be kept up-to-date with other packages on system that run > only release versions of FreeBSD. (And as written before, I do not > suggest to remove the timezone files from base at all.) > > > But, three things. First, we update leapseconds.list as soon as it is > > announce. Second, there is no way to get just these files updated: they > > come for free with a rebuild or and update using the beta pkgbase, but > > there is no automatic way to just get these. Third, there is an daily > > cron job that fetches leap-seconds.list if you have ntpd enabled and you > > are on the internet. > > Yes, if only the leap-seconds are required, this helps get the time > synchronized - but is quite different from timezone file updates. > > > So no TZ update outside an os upgrade, but the leap seconds file updates > > at the speed of NIST... > > The OP did not ask for leap-second updates but for timezone files, > if I understand his mail correctly. > Yes. But I know him from another list I'm on and knew the back story. How does FreeBSD know about leap seconds and what mechanism does it use to keep up to date was the topic there. Warner