mailing list of musl libc
 help / color / mirror / code / Atom feed
From: orc <orc@sibserver.ru>
To: musl@lists.openwall.com
Subject: Re: syslog() always sends GMT timestamps
Date: Sat, 01 Feb 2014 17:38:04 +0800	[thread overview]
Message-ID: <893bdc5e-e8a8-43fd-b2cf-3d8afc3e46c5@email.android.com> (raw)
In-Reply-To: <20140201005419.GZ24286@brightrain.aerifal.cx>

1 февраля 2014 г. 8:54:19 KRAT, Rich Felker <dalias@aerifal.cx> пишет:
>On Thu, Jan 30, 2014 at 01:04:13PM +0100, Szabolcs Nagy wrote:
>> * Rich Felker <dalias@aerifal.cx> [2014-01-29 23:33:44 -0500]:
>> > 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.
>> 
>> btw currently syslog does not print year so even if
>> at a later point one tries to parse the date and
>> display it in local time it will be hard to do so
>> 
>> imo the standard timestamp format is '%Y-%m-%d %H:%M:%S'
>> (maybe with T instead of space, but that's less readable)
>> it is a bit longer than the current one, but at least
>> clear, not nl_langinfo dependent (in case someone adds
>> LC_TIME support for other languages) and reversible
>> 
>> (the real iso8601/rfc3339 standard is '%Y-%m-%dT%H:%M:%SZ')
>
>I'd like more input from users. I don't think this is something we
>should change immediately before 1.0 or in the 1.0.x stable series,
>but you've raised very good points that should be addressed at some
>point. If we add build customization at some point in the future, this
>may be an area we should consider allowing some degree of
>customization. But of course I'm a bit hesitant to start doing that.
>

I already patched my musl tree to run with localtime since it does not affect much of internal state as you noted.
IMHO I think musl wiki should have article about customization patches like this rather than configure options.
The libc itself is strict and sane.

>Rich




      parent reply	other threads:[~2014-02-01  9:38 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
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 [this message]

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=893bdc5e-e8a8-43fd-b2cf-3d8afc3e46c5@email.android.com \
    --to=orc@sibserver.ru \
    --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).