From: "cpt.arsemerica.yahoo.com via supervision" <supervision@list.skarnet.org>
To: "supervision@list.skarnet.org" <supervision@list.skarnet.org>,
Laurent Bercot <ska-supervision@skarnet.org>
Subject: Re: [svlogd] / -ttt / why UTC?
Date: Thu, 6 Apr 2023 12:47:14 +0000 (UTC) [thread overview]
Message-ID: <1799016718.299578.1680785234404@mail.yahoo.com> (raw)
In-Reply-To: <em849e5c8a-51be-4210-b18e-2ff0a4fa7646@cdceff30.com>
Laurent Bercot <ska-supervision@skarnet.org> wrote:
> If your system clock is set to TAI-10, [...]
>
I don't know exactly what u mean with "TAI-10".
I guess u are refering to those 10seconds
that were the initial difference between UTC and TAI at the start of 1972...
So it should be TAI-00:00:10...
> [...] then *all* the time-handling
> software on your machine must be aware of it,
>
here i disagree a little bit:
As long as the software uses glibc's time functions to break down
"seconds since the start of 1970* to year, month, mday, hours, minutes, seconds,
the software does not need any patches...
Ur link is a little bit misleading or outdated in that point...
exim, fetchmail, dma and s-nail need(ed) a change, because:
They omitted the non-zero seconds
instead of converting the timestamp to UTC and
printing the timezone as -00:00 (with a minus).
> I don't think you'll be able to keep running Void with a full TAI-10
>
What would be wrong about the "-tttt" (localtime time stamp) option?
Then I would not have to build/write my own *log daemon...
And svlogd just needs to use localtime_r(3)...
next prev parent reply other threads:[~2023-04-06 12:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1799590563.259018.1680775861585.ref@mail.yahoo.com>
2023-04-06 10:11 ` cpt.arsemerica.yahoo.com via supervision
2023-04-06 11:02 ` Laurent Bercot
2023-04-06 12:47 ` cpt.arsemerica.yahoo.com via supervision [this message]
2023-04-06 18:12 ` Laurent Bercot
2023-04-06 20:37 ` cpt.arsemerica.yahoo.com via supervision
2023-04-09 6:11 ` Jonathan de Boyne Pollard
2023-04-06 23:21 ` Alexis
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=1799016718.299578.1680785234404@mail.yahoo.com \
--to=supervision@list.skarnet.org \
--cc=cpt.arsemerica@yahoo.com \
--cc=ska-supervision@skarnet.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).