mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Szabolcs Nagy <nsz@port70.net>
To: musl@lists.openwall.com
Subject: Re: [PATCHv2] Add support for leap seconds in zoneinfo files
Date: Fri, 6 Dec 2013 14:27:29 +0100	[thread overview]
Message-ID: <20131206132729.GD1685@port70.net> (raw)
In-Reply-To: <20131206125055.GA24286@brightrain.aerifal.cx>

* Rich Felker <dalias@aerifal.cx> [2013-12-06 07:50:55 -0500]:
> On Fri, Dec 06, 2013 at 10:37:56AM +0000, Laurent Bercot wrote:
> >  Yes, people using TAI-10 should also be using right/ timezones instead of
> > posix/ ones. That's why TZ as a test is appealing: it ensures consistency.
> > But at that level it's entirely the admin's responsibility to have
> > consistent configuration: leap-second-conscious admins won't mind doing
> > some extra work to have a setting that pleases them.
> 
> The problem with this approach is that an individual user may unset
> $TZ or set it to a POSIX-syntax timezone such as "UTC" on a system
> where the system clock is using TAI-10. Users generally expect this to
> work, and their expectation is justified. Valid scripts might even use
> TZ=UTC as part of their functionality.

this just means the tz data depends on the timescale used

if an admin is willing to do the leapsecond hassle then
putting the "right" files into /usr/share/zoneinfo can
be done as well, TZ=UTC will work

the current practice of using TZ=right/foo is wrong, it
means that gmtime-localtime is not the tzoffset or gmtime
depends on TZ

ie. an admin can choose to set up different timescale, but
then leapseconds and zoneinfo must be configured in the
filesystem accordingly (and regularly updated)


  reply	other threads:[~2013-12-06 13:27 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-26 18:53 [PATCH] " Laurent Bercot
2013-11-26 18:59 ` Laurent Bercot
2013-11-26 23:32 ` Rich Felker
2013-11-27  1:06   ` Rich Felker
2013-11-27  4:10   ` Laurent Bercot
2013-11-27  4:25     ` Rich Felker
2013-11-27  5:53       ` Laurent Bercot
2013-11-27 18:43         ` Szabolcs Nagy
2013-11-27 20:33           ` Laurent Bercot
2013-12-05  1:13             ` [PATCHv2] " Laurent Bercot
2013-12-05  5:18               ` Szabolcs Nagy
2013-12-05  8:58                 ` Laurent Bercot
2013-12-05 14:21                   ` Szabolcs Nagy
2013-12-05 14:43               ` Rich Felker
2013-12-05 16:31                 ` Laurent Bercot
2013-12-05 16:40                   ` Rich Felker
2013-12-06  0:36                     ` Laurent Bercot
2013-12-06  0:45                       ` Rich Felker
2013-12-06  1:15                         ` Laurent Bercot
2013-12-06  5:31                           ` Szabolcs Nagy
2013-12-06 10:48                             ` Laurent Bercot
2013-12-06 11:38                               ` Raphael Cohn
2013-12-06 23:29                                 ` Laurent Bercot
2013-12-07  2:31                                   ` Rich Felker
2013-12-07  4:02                                     ` Szabolcs Nagy
2013-12-07  8:52                                     ` Laurent Bercot
2013-12-06  6:29                           ` Rich Felker
2013-12-06 10:37                             ` Laurent Bercot
2013-12-06 12:50                               ` Rich Felker
2013-12-06 13:27                                 ` Szabolcs Nagy [this message]
2013-12-06 15:48                                   ` Rich Felker

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20131206132729.GD1685@port70.net \
    --to=nsz@port70.net \
    --cc=musl@lists.openwall.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).