mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Patrick Oppenlander <pattyo.lists@gmail.com>
To: musl@lists.openwall.com
Subject: Re: detect timezone changes by monitoring /etc/localtime (like glibc)
Date: Tue, 13 Jun 2017 09:08:15 +1000	[thread overview]
Message-ID: <4c950249-6330-543c-4279-3291bf4ead58@gmail.com> (raw)
In-Reply-To: <20170609121502.GO1627@brightrain.aerifal.cx>

On 09/06/17 22:15, Rich Felker wrote:
> On Fri, Jun 09, 2017 at 05:15:40PM +1000, Patrick Oppenlander wrote:
>> During some recent testing I came across a bug when adjusting timezones on an
>> embedded system by changing /etc/localtime. The cause ended up being a
>> behavioural difference between glibc and musl.
> 
> This difference is intentional; I believe there are past discussions
> in the list archives.
> 

I found https://marc.info/?l=musl&m=141374003126007&w=2 which was helpful.

Performance could be addressed (inotify?) but it's all moot anyway given
the other issues mentioned.

> 
> In order for asynchronous timezone changes to be safe, the API would
> have to be such that you make one call to get the current timezone,
> then pass it as an argument to functions depending on the timezone, so
> that the application has control of which timezone is getting used in
> each call.
> 

This is how the WIN32 API is implemented.

		Patrick


  parent reply	other threads:[~2017-06-12 23:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-09  7:15 Patrick Oppenlander
2017-06-09 12:15 ` Rich Felker
2017-06-10  3:36   ` A. Wilcox
2017-06-10  9:57     ` u-uy74
2017-06-10 12:23       ` Rich Felker
2017-06-10 13:23         ` u-uy74
2017-06-12 23:08   ` Patrick Oppenlander [this message]
2017-06-12 23:19     ` Rich Felker
2017-06-12 23:49       ` Patrick Oppenlander
2017-06-12 23:58         ` 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=4c950249-6330-543c-4279-3291bf4ead58@gmail.com \
    --to=pattyo.lists@gmail.com \
    --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).