Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 29 Jan 2014 23:33:44 -0500
From: Rich Felker <>
Subject: Re: syslog() always sends GMT timestamps

On Wed, Jan 29, 2014 at 07:45:25PM +0800, orc wrote:
> Thank you for your detailed explanation about cross-process and
> cross-user issues. Since my systems are probably not going to be
> true multi-user interconnected and sharing resources (say, for
> example, sending logs to central syslog server), I want to keep
> "old" behavior of syslog(). Can you give advices how I can do that
> in more safe way? If it is not possible, what breakage can occur if
> I will go with localtime_r()?
> Thanks!

Really it's unlikely to break anything if you just use localtime_r,
but the behavior is testably/observably incorrect per the standard and
could interact badly with multithreaded programs which change their
own environments at runtime (note that the same breakage probably
occurs on glibc and elsewhere though; musl just tries to be better
than that).

So really this is a matter you could pretty easily change locally, but
where for correctness and robustness the change isn't acceptable
upstream. If you (or others) still have interest in trying to get
syslog with local time upstream, we'll need to have a discussion on
how it could be done safely.


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.