[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ecf2742a-6cab-cc00-16ab-589fad07b8db@cs.ucla.edu>
Date: Tue, 13 Aug 2019 10:49:03 -0700
From: Paul Eggert <eggert@...ucla.edu>
To: Linus Torvalds <torvalds@...ux-foundation.org>,
Arnd Bergmann <arnd@...db.de>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Thomas Gleixner <tglx@...utronix.de>,
John Stultz <john.stultz@...aro.org>,
Alexandre Belloni <alexandre.belloni@...tlin.com>,
Stephen Boyd <sboyd@...nel.org>,
Florian Weimer <fweimer@...hat.com>,
Theodore Ts'o <tytso@....edu>,
"H. Peter Anvin" <hpa@...or.com>,
Palmer Dabbelt <palmer@...belt.com>,
Alistair Francis <alistair.francis@....com>,
GNU C Library <libc-alpha@...rceware.org>,
Karel Zak <kzak@...hat.com>,
Lennart Poettering <lennart@...ttering.net>,
OGAWA Hirofumi <hirofumi@...l.parknet.co.jp>
Subject: Re: New kernel interface for sys_tz and timewarp?
Linus Torvalds wrote:
> I assume/think that glibc uses (a) environment
> variables and (b) a filesystem-set default (per-user file with a
> system-wide default? I don't know what people do).
glibc relies on the TZ environment variable, with a system-wide default
specified in /etc/localtime or suchlike (there is no per-user default). glibc
ignores the kernel's 'struct timezone' settings for of this, as 'struct
timezone' is obsolete/vestigial and doesn't contain enough info to do proper
conversions anyway.
I've been thinking of adding NetBSD's localtime_rz etc. functions to glibc.
These functions let user programs specify the time zone for each conversion
between time_t and local time, and simplify and/or speed up applications dealing
with many requests coming from different time zones. These functions also ignore
'struct timezone'.
There's no need to put any of this stuff into the kernel.
Powered by blists - more mailing lists