From: BurnZeZ@feline.systems
To: 9front@9front.org
Subject: Re: [9front] syslog(2) change
Date: Wed, 10 Feb 2016 17:41:34 -0500 [thread overview]
Message-ID: <1f978b238a980348b347e926d3620477@utsuho.znet> (raw)
In-Reply-To: <5b700121babb21f8e721550f9815085f@ghost.attlocal.net>
On Wed Feb 10 15:28:40 EST 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
>
I assume latency is the primary reason not to. If you're running a
bunch of scripts that are accessing files all over the place, you
might have a problem. One useful example I can think of would be
having some remote machine that is primarily used as a remote gateway.
You're right though, I can see why someone might avoid doing this.
On Wed Feb 10 16:08:12 EST 2016, khm@sciops.net wrote:
> On Wed, Feb 10, 2016 at 09:57:36PM +0100, Julius Schmidt wrote:
> > I do much prefer something like yyyy-mm-dd... over burnzez' suggestion.
>
> If you're going to put timezones in the logfiles, you pretty much have
> to use ISO-8601 date formats, and resolve to stick to numeric offsets.
> As we're discovering on irc, trying to convert from abbreviations to
> meaningul data is a fool's game. Switching to YYYY-MM-DDTHH:MM:SS+HH:MM
> is the only sane option.
>
> khm
>
cirno Feb 9 20:38:55 Hung up on 8.8.8.8; claimed to be fbi.gov
cirno 1455068335 Hung up on 8.8.8.8; claimed to be fbi.gov
cirno 2016-02-09T20:38:55-0500 Hung up on 8.8.8.8; claimed to be fbi.gov
I still prefer the terseness of seconds since the epoch, but ISO-8601 is
at least machine readable.
next prev parent reply other threads:[~2016-02-10 22:41 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
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 [this message]
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=1f978b238a980348b347e926d3620477@utsuho.znet \
--to=burnzez@feline.systems \
--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).