From: John W Higgins <wishdev@gmail.com>
To: Supervision <supervision@list.skarnet.org>
Subject: Re: Following log directories
Date: Thu, 25 Jun 2020 15:32:15 -0700 [thread overview]
Message-ID: <CAPhAwGzuZzYVVGhcm5pudimk0f4iDgS_qHY2Drv+wusd0CayJA@mail.gmail.com> (raw)
In-Reply-To: <CACsCw1MJ2GsfYtEGpj8WN6Ta=aVAqkbFp03TDnAJRFnPK964hA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 953 bytes --]
One thing to remember about tools like this is that s6 is very precise with
it's implemenation of TAI64N - it uses leap seconds.
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.
So just make sure you check that the timestamps are what you expect them to
be with non s6 tools.
John
[1] - http://lnav.org/
On Thu, Jun 25, 2020 at 3:08 PM Carl Winbäck <c@tunnel53.net> wrote:
> On Thu, 25 Jun 2020 at 17:00, Guillermo wrote:
> > And it appears to be compatible, indeed, as long as s6-log is invoked
> > with the 't' directive (prepend timestamp in TAI64N format), to match
> > the logging file format expected by follow-log-directories, as stated
> > in its documentation.
>
> Neat! Thank you Guillermo for this information.
>
> Best regards,
> Carl
>
next prev parent reply other threads:[~2020-06-25 22:32 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 [this message]
2020-06-26 0:09 ` Laurent Bercot
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=CAPhAwGzuZzYVVGhcm5pudimk0f4iDgS_qHY2Drv+wusd0CayJA@mail.gmail.com \
--to=wishdev@gmail.com \
--cc=supervision@list.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).