From: Julius Schmidt <aiju@phicode.de>
To: 9front@9front.org
Subject: Re: [9front] syslog(2) change
Date: Wed, 10 Feb 2016 21:57:36 +0100 (CET) [thread overview]
Message-ID: <alpine.LNX.2.00.1602102154330.6016@phi> (raw)
In-Reply-To: <5b700121babb21f8e721550f9815085f@ghost.attlocal.net>
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.
I do much prefer something like yyyy-mm-dd... over burnzez' suggestion.
aiju
On Wed, 10 Feb 2016, sl@stanleylieber.com wrote:
>>> This seems like the obvious question upon which all of this hinges. This is
>>> almost certainly a rare case.
>>
>> I didn't consider this a strange thing to do. Running a bunch of
>> nodes from a single install means only maintaining one filesystem.
>> Nonetheless, netbooted terminals in a different timezone will have
>> the same issue.
>
> Systems in different timezones sharing an fs is precisely the "rare
> case" I was describing. Can you guess why this case is rare?
>
> sl
>
next prev parent reply other threads:[~2016-02-10 20:57 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
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 [this message]
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=alpine.LNX.2.00.1602102154330.6016@phi \
--to=aiju@phicode.de \
--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).