Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: rbowman <bowman@montana.com>
Newsgroups: comp.os.linux.misc
Subject: Re: Date formatting.
Date: 30 Sep 2025 02:08:11 GMT
Lines: 12
Message-ID: <mk0scbF77pcU1@mid.individual.net>
References: <1835a5c81ceedfd3$44418$19313$802601b3@news.usenetexpress.com> <20250414092849.00004cdd@gmail.com> <pan$630f$11fc0600$4376005a$ad574581@linux.rocks> <87wmbcguz9.fsf@somewhere.edu> <pan$4f5c8$f12b9163$46e2db5$f503da29@linux.rocks> <87wm5u9jh8.fsf@somewhere.edu> <68cec4ae$0$16841$426a74cc@news.free.fr> <pan$22d08$c7d3d6c5$93f27de1$98b75aed@linux.rocks> <68ceec3c$0$419$426a74cc@news.free.fr> <pan$f146c$86520db6$e8d55afa$81b97306@linux.rocks> <68d012d4$0$16839$426a74cc@news.free.fr> <pan$1d272$d3891b48$ebe7af94$67ee5eca@linux.rocks> <68d7f84d$0$12939$426a74cc@news.free.fr> <18692cf2a1c4c4fa$28998$2650548$802601b3@news.usenetexpress.com> <10bb1s4$29c4m$1@dont-email.me> <20250929091131.00000dc4@gmail.com> <FIyCQ.112782$DQYd.18287@fx16.iad> <jvqqqlxnbk.ln2@Telcontar.valinor> <10befmu$33rad$1@dont-email.me>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-Trace: individual.net szz1mFvMxpcSduRCdAePlgfV9XR3SppnJdFhjD+JJQ86hkInCW
Cancel-Lock: sha1:cE+ti0LXvkIcnIcb+B7+0M8a84E= sha256:asiCHXZ40SbGfIcOmX6ZPWfGWuzCBnNa24RWAANCCJ8=
User-Agent: Pan/0.162 (Pokrosvk)
Xref: csiph.com comp.os.linux.misc:75440

On Mon, 29 Sep 2025 18:30:06 +0100, Pancho wrote:

> I like YYYYMMDD too, but the real epiphany moment for me was when I
> realised that all dates should be handled internally UTC, Unix time,
> and that output format, display, is just a user preference.

That would sometimes throw our support people. When you harvest logs from 
a site the times match their wall clock time. If you grab raw data where 
the time was stored as a time_t value, reporting tools will use 
localtime() to when formatting the data, leading to 'Why are the times off 
by two hours?'