supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: "Laurent Bercot" <ska-supervision@skarnet.org>
To: "John W Higgins" <wishdev@gmail.com>,
	Supervision <supervision@list.skarnet.org>
Subject: Re: Following log directories
Date: Fri, 26 Jun 2020 00:09:25 +0000	[thread overview]
Message-ID: <ema0f5d325-6aad-4c94-b6de-18a3badd39f9@elzian> (raw)
In-Reply-To: <CAPhAwGzuZzYVVGhcm5pudimk0f4iDgS_qHY2Drv+wusd0CayJA@mail.gmail.com>

>I use lnav [1] for a similar concept and it parses TAI64N but it does not
>deal with leap seconds so my timestamps were off by like 20 seconds (or
>something similar). I had to modify the code to handle the leap seconds.

  TAI64N labels represent TAI time, which is linear; when you need a
leap second table is when you want to convert TAI labels to UTC or
local time.

  My guess is that lnav just prints the TAI time as if it were UTC,
which indeed will print a time that, in 2020, is too high by 27 seconds.
If that is the case, it's a bug that would be worth reporting to lnav.

--
  Laurent


  reply	other threads:[~2020-06-26  0:09 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 [this message]
2020-06-26  0:49           ` John W Higgins
2020-06-26  9:24             ` Jan Braun
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=ema0f5d325-6aad-4c94-b6de-18a3badd39f9@elzian \
    --to=ska-supervision@skarnet.org \
    --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).