From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from phicode.de ([136.243.147.240]) by ur; Wed Feb 10 15:57:56 EST 2016 Received: (qmail 16741 invoked from network); 10 Feb 2016 20:57:36 -0000 Received: from localhost (127.0.0.1) by localhost with SMTP; 10 Feb 2016 20:57:36 -0000 Date: Wed, 10 Feb 2016 21:57:36 +0100 (CET) From: Julius Schmidt X-X-Sender: aiju@phi To: 9front@9front.org Subject: Re: [9front] syslog(2) change In-Reply-To: <5b700121babb21f8e721550f9815085f@ghost.attlocal.net> Message-ID: References: <1270b9585a3e327733049d87e8a08103@utsuho.znet> <50a1e90923c69e7c710766ab431c23a8@utsuho.znet> <1455120937435-0fca18ba-a33032ef-afc32a2e@stanleylieber.com> <68c8b9c471a28126f0ca4ddfb1f8f034@utsuho.znet> <5b700121babb21f8e721550f9815085f@ghost.attlocal.net> User-Agent: Alpine 2.00 (LNX 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: element shader hosting firewall 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 >