mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@aerifal.cx>
To: musl@lists.openwall.com
Subject: Re: syslog() always sends GMT timestamps
Date: Wed, 29 Jan 2014 23:33:44 -0500	[thread overview]
Message-ID: <20140130043344.GR24286@brightrain.aerifal.cx> (raw)
In-Reply-To: <770108a1-99d7-4ef0-b860-b045866c9895@email.android.com>

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.

Rich


  reply	other threads:[~2014-01-30  4:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-28 11:39 orc
2014-01-28 17:11 ` Rich Felker
2014-01-29 11:45   ` orc
2014-01-30  4:33     ` Rich Felker [this message]
2014-01-30 12:04       ` Szabolcs Nagy
2014-02-01  0:54         ` Rich Felker
2014-02-01  1:26           ` Laurent Bercot
2014-02-01  9:09             ` Szabolcs Nagy
2014-02-01 11:01               ` Christian Wiese
2014-02-01 15:48               ` Laurent Bercot
2014-02-01 17:07                 ` Paul Schutte
2014-02-01  9:38           ` orc

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=20140130043344.GR24286@brightrain.aerifal.cx \
    --to=dalias@aerifal.cx \
    --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).