Date: Tue, 13 Jun 2017 09:08:15 +1000 From: Patrick Oppenlander <pattyo.lists@...il.com> To: musl@...ts.openwall.com Subject: Re: detect timezone changes by monitoring /etc/localtime (like glibc) 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
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.