[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20141019130029.416ada2c@vostro>
Date: Sun, 19 Oct 2014 13:00:29 +0300
From: Timo Teras <timo.teras@....fi>
To: u-wsnj@...ey.se
Cc: musl@...ts.openwall.com
Subject: Re: do_tzset() prevents reusing the same name of a timezone
file
On Sun, 19 Oct 2014 11:36:11 +0200
u-wsnj@...ey.se wrote:
> On Sun, Oct 19, 2014 at 11:26:08AM +0400, Королев Сергей wrote:
> > The constant TZ pointing to the symlink used to apply timezone
> > settings for all active processes in the system on the fly. This
> > needs for proper logging with the syslog.
>
> I may misunderstand what you mean by "proper logging" but logging
> in local time when the time zone is expected to change does not look
> reliable to me.
>
> I would suggest telling the syslog daemon to work in UTC (by setting
> its TZ variable to a corresponding value).
> Then you always have consistent logs and do not have to analyze
> which time zone a certain logged event happened in.
Perhaps logging is not best example here. But I think the original
point is valid.
If I use TZ=:localtime, and /etc/localtime symlink is updated to point
to different file, or the tzdata is upgraded and the file is updated,
long running processes should pick up the changes.
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.
