From: Guillermo <gdiazhartusch@gmail.com>
To: Supervision <supervision@list.skarnet.org>
Subject: Re: Following log directories
Date: Thu, 25 Jun 2020 11:52:40 -0300 [thread overview]
Message-ID: <CADQ2Nw9uHy8Ua2aGUB=pLf__FzV9Jamhrh29CrbaZk+dAAMuoQ@mail.gmail.com> (raw)
In-Reply-To: <CADQ2Nw8eYNmumd6vxs-pg2-u6NhF2dTW8U591eDm2yd5fyNWjg@mail.gmail.com>
El jue., 25 jun. 2020 a las 10:20, Guillermo escribió:
>
> El jue., 25 jun. 2020 a las 6:27, Carl Winbäck escribió:
>
> > Does anyone know if the follow-log-directories tool[1] from the nosh
> > suite is compatible with logs produced by s6-log?
>
> Let's find out. I'll test that.
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.
Also, note that follow-log-directories is a daemon, so it will keep
running and outputting log lines until killed, once it catches up with
the logging directory. TAI64N timestamps are not decoded, so if you
want them in human-readable format, pipe its standard output to
s6-tai64nlocal.
You might also want to separate follow-log-directories's standard
output stream from its standard error stream, since the program is
somewhat chatty during catch-ups and during logdir rotations.
G.
next prev parent reply other threads:[~2020-06-25 14:52 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 [this message]
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
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='CADQ2Nw9uHy8Ua2aGUB=pLf__FzV9Jamhrh29CrbaZk+dAAMuoQ@mail.gmail.com' \
--to=gdiazhartusch@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).