From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from ds.inri.net ([107.191.103.21]) by ur; Wed Feb 10 16:06:51 EST 2016
Received: from ghost.inri ([107.191.103.21]) by ds; Wed Feb 10 16:06:48 EST 2016
Date: Wed, 10 Feb 2016 16:06:39 -0500
From: sl@stanleylieber.com
To: 9front@9front.org
Subject: Re: [9front] syslog(2) change
Message-ID: <4b69a6e5a9cac5df34f7112f58749050@ghost.attlocal.net>
In-Reply-To: <alpine.LNX.2.00.1602102154330.6016@phi>
References: <1270b9585a3e327733049d87e8a08103@utsuho.znet>
	<D5041DCA-9744-4636-AEDE-68F4A104EB5F@ar.aichi-u.ac.jp>
	<50a1e90923c69e7c710766ab431c23a8@utsuho.znet>
	<FD0188D4-7F79-4FBD-9DA2-FA3F0F714511@ar.aichi-u.ac.jp>
	<1455120937435-0fca18ba-a33032ef-afc32a2e@stanleylieber.com>
	<68c8b9c471a28126f0ca4ddfb1f8f034@utsuho.znet>
	<5b700121babb21f8e721550f9815085f@ghost.attlocal.net>
	<alpine.LNX.2.00.1602102154330.6016@phi>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: standard-based API standard 

> I'm in favour of putting timezones in log files. I know it may seem
> pedantic, but imagine a program parsing log files that needs to convert
> into unix timestamp.  It seems silly to require such a program to be
> able to map hosts to timezones.  Adding a timezone identifier to log
> files seems like a trivial change that would remove any ambiguity about
> the exact UTC time of a log entry.

Wait, this approaches a rationale.

sl