From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/4531 Path: news.gmane.org!not-for-mail From: Rich Felker Newsgroups: gmane.linux.lib.musl.general Subject: Re: syslog() always sends GMT timestamps Date: Fri, 31 Jan 2014 19:54:19 -0500 Message-ID: <20140201005419.GZ24286@brightrain.aerifal.cx> References: <500a674a-fd43-49f5-99b8-6fd0b18ef5a2@email.android.com> <20140128171153.GL24286@brightrain.aerifal.cx> <770108a1-99d7-4ef0-b860-b045866c9895@email.android.com> <20140130043344.GR24286@brightrain.aerifal.cx> <20140130120413.GT1685@port70.net> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1391216067 14604 80.91.229.3 (1 Feb 2014 00:54:27 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 1 Feb 2014 00:54:27 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-4535-gllmg-musl=m.gmane.org@lists.openwall.com Sat Feb 01 01:54:36 2014 Return-path: Envelope-to: gllmg-musl@plane.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by plane.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1W9Oqx-0003D4-Sj for gllmg-musl@plane.gmane.org; Sat, 01 Feb 2014 01:54:35 +0100 Original-Received: (qmail 18356 invoked by uid 550); 1 Feb 2014 00:54:33 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Original-Received: (qmail 18344 invoked from network); 1 Feb 2014 00:54:32 -0000 Content-Disposition: inline In-Reply-To: <20140130120413.GT1685@port70.net> User-Agent: Mutt/1.5.21 (2010-09-15) Xref: news.gmane.org gmane.linux.lib.musl.general:4531 Archived-At: On Thu, Jan 30, 2014 at 01:04:13PM +0100, Szabolcs Nagy wrote: > * Rich Felker [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. Rich