[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20131206154857.GB24286@brightrain.aerifal.cx>
Date: Fri, 6 Dec 2013 10:48:57 -0500
From: Rich Felker <dalias@...ifal.cx>
To: musl@...ts.openwall.com
Subject: Re: [PATCHv2] Add support for leap seconds in zoneinfo files
On Fri, Dec 06, 2013 at 02:27:29PM +0100, Szabolcs Nagy wrote:
> * Rich Felker <dalias@...ifal.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
No, UTC is not a file. Since UTC matches the POSIX syntax for
timezones it's required to be interpreted as a STD[off[DST[off]]]
rather than as a filename.
Rich
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
