From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from ar.aichi-u.ac.jp ([202.250.160.40]) by ur; Wed Feb 10 08:52:26 EST 2016
Received: from [192.168.0.249] ([115.36.94.245]) by ar; Wed Feb 10 22:52:16 JST 2016
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
Subject: Re: [9front] syslog(2) change
From: arisawa <arisawa@ar.aichi-u.ac.jp>
In-Reply-To: <50a1e90923c69e7c710766ab431c23a8@utsuho.znet>
Date: Wed, 10 Feb 2016 22:52:15 +0900
Content-Transfer-Encoding: quoted-printable
Message-Id: <FD0188D4-7F79-4FBD-9DA2-FA3F0F714511@ar.aichi-u.ac.jp>
References: <1270b9585a3e327733049d87e8a08103@utsuho.znet> <D5041DCA-9744-4636-AEDE-68F4A104EB5F@ar.aichi-u.ac.jp> <50a1e90923c69e7c710766ab431c23a8@utsuho.znet>
To: 9front@9front.org
X-Mailer: Apple Mail (2.2104)
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: strategy template 

I don=E2=80=99t understand what real problems you want to resolve.
are your log files shard among cpu servers that are located in different =
time zone?

> 2016/02/10 21:14=E3=80=81BurnZeZ@feline.systems =E3=81=AE=E3=83=A1=E3=83=
=BC=E3=83=AB=EF=BC=9A
>=20
>> I prefer
>> cirno 2016-02-01 20:38:55 Hung up on 8.8.8.8; claimed to be fbi.gov
>> instead of
>> cirno Feb  9 20:38:55 Hung up on 8.8.8.8; claimed to be fbi.gov
>=20
> This doesn't address the timezone problem, which is arguably the
> biggest concern.  The first thing I thought of was simply including
> the timezone, but that really just means more crap on each line
>=20
> Another way is to just imply GMT and exclude specifying it in the
> date/time, but then the logs don't appear different, so it's not easy
> to tell when the behavior was corrected if you're looking back at your
> logs in the future.
>=20
>=20
>> your
>> 1455068335 cirno Hung up on 8.8.8.8; claimed to be fbi.gov
>> is too radical, I think.
>=20
> Perhaps, but it seems to me like the simplest fix.