supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Jan Braun <janbraun@gmx.de>
To: John W Higgins <wishdev@gmail.com>
Cc: Supervision <supervision@list.skarnet.org>
Subject: Re: Following log directories
Date: Fri, 26 Jun 2020 11:24:21 +0200	[thread overview]
Message-ID: <20200626092421.GA15247@klumpi.ignorelist.com> (raw)
In-Reply-To: <CAPhAwGzBtFJOPG_GOu+TFu9fXTJ-kPUDJ_sM98A3uzvSZEhhgw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1656 bytes --]

John W Higgins schrob:
> I meant nothing towards s6 - but daemontools does not deal with leap
> seconds (or at least it cetainly looks that way from my foolish viewpoint).

Daemontools assumes that time(3) returns TAI-like time (seconds actually
elapsed since the epoch). That's a rather sane approach that allows to
do time calculations with complete disregard for leap seconds and time
zones. And for communication with the user, you consult tables listing
the effects of the erratic movements of the earth and politicians,
respectively. These tables are usually shipped in the "right/" tzdata
directory, used by setting e.g. TZ=right/Europe/Lisbon .

Unfortunately, POSIX mandates that time(3) returns UTC-like time instead
(arithmetic difference between the epoch and now, calculated as if leap
seconds didn't exist). That's what most systems do, also because the NTP
protocol runs on UTC, and NTP clients by default set computer's clocks
to UTC-like timestamps. The obvious disadvantage is the need to keep
leap seconds in mind when doing any calculation, or to accept being
wrong by up to 27 (as of now) seconds. And then consult tables for
politician effects only, e.g. TZ=Europe/Lisbon or equivalently
TZ=posix/Europe/Lisbon .

So yes, daemontools does not deal with leap seconds, because that's the
smart thing to do. ;)
At least if you can configure your NTP client to support that scenario.


> I was just pointing out that there is a second check which may need to be
> applied to make sure the viewer is providing the information one believes
> they are seeing.

Yes. I hope I could provice some useful/interesting background.
Cheers,
    Jan

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2020-06-26  9:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-25  9:27 Carl Winbäck
2020-06-25 13:20 ` Guillermo
2020-06-25 14:52   ` Guillermo
2020-06-25 22:08     ` Carl Winbäck
2020-06-25 22:32       ` John W Higgins
2020-06-26  0:09         ` Laurent Bercot
2020-06-26  0:49           ` John W Higgins
2020-06-26  9:24             ` Jan Braun [this message]
2020-06-26  9:27             ` Laurent Bercot
2020-06-26 19:52               ` John W Higgins
2020-06-27  6:12                 ` Laurent Bercot
2020-06-27  7:33             ` Jonathan de Boyne Pollard
2020-06-28 19:38               ` Guillermo
2020-06-27  7:33         ` Jonathan de Boyne Pollard

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=20200626092421.GA15247@klumpi.ignorelist.com \
    --to=janbraun@gmx.de \
    --cc=supervision@list.skarnet.org \
    --cc=wishdev@gmail.com \
    /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).