From: arisawa <arisawa@ar.aichi-u.ac.jp>
To: 9front@9front.org
Subject: Re: [9front] syslog(2) change
Date: Wed, 10 Feb 2016 22:52:15 +0900 [thread overview]
Message-ID: <FD0188D4-7F79-4FBD-9DA2-FA3F0F714511@ar.aichi-u.ac.jp> (raw)
In-Reply-To: <50a1e90923c69e7c710766ab431c23a8@utsuho.znet>
I don’t 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、BurnZeZ@feline.systems のメール:
>
>> 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
>
> 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
>
> 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.
>
>
>> your
>> 1455068335 cirno Hung up on 8.8.8.8; claimed to be fbi.gov
>> is too radical, I think.
>
> Perhaps, but it seems to me like the simplest fix.
next prev parent reply other threads:[~2016-02-10 13:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 5:03 BurnZeZ
2016-02-10 5:08 ` [9front] " Devon H. O'Dell
2016-02-10 5:41 ` arisawa
2016-02-10 12:14 ` BurnZeZ
2016-02-10 13:52 ` arisawa [this message]
2016-02-10 16:15 ` stanley lieber
2016-02-10 20:25 ` BurnZeZ
2016-02-10 20:28 ` sl
2016-02-10 20:57 ` Julius Schmidt
2016-02-10 21:06 ` sl
2016-02-10 21:08 ` Kurt H Maier
2016-02-10 21:22 ` Devon H. O'Dell
2016-02-10 21:24 ` sl
2016-02-10 22:41 ` BurnZeZ
2016-02-11 3:02 ` arisawa
2016-02-10 16:06 ` Kurt H Maier
2016-02-10 20:24 ` BurnZeZ
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=FD0188D4-7F79-4FBD-9DA2-FA3F0F714511@ar.aichi-u.ac.jp \
--to=arisawa@ar.aichi-u.ac.jp \
--cc=9front@9front.org \
/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.
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).