From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org
X-Spam-Level: 
X-Spam-Status: No, score=-1.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID,
	DKIM_VALID_AU,FREEMAIL_FROM,MAILING_LIST_MULTI autolearn=ham
	autolearn_force=no version=3.4.4
Received: (qmail 15504 invoked from network); 25 Jun 2020 14:52:54 -0000
Received: from alyss.skarnet.org (95.142.172.232)
  by inbox.vuxu.org with ESMTPUTF8; 25 Jun 2020 14:52:54 -0000
Received: (qmail 5140 invoked by uid 89); 25 Jun 2020 14:53:18 -0000
Mailing-List: contact supervision-help@list.skarnet.org; run by ezmlm
Sender: <supervision@list.skarnet.org>
Precedence: bulk
List-Post: <mailto:supervision@list.skarnet.org>
List-Help: <mailto:supervision-help@list.skarnet.org>
List-Unsubscribe: <mailto:supervision-unsubscribe@list.skarnet.org>
List-Subscribe: <mailto:supervision-subscribe@list.skarnet.org>
List-Id: <supervision.list.skarnet.org>
Received: (qmail 5130 invoked from network); 25 Jun 2020 14:53:18 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20161025;
        h=mime-version:references:in-reply-to:from:date:message-id:subject:to
         :content-transfer-encoding;
        bh=vCsY5rvycDEqZVKTnBTuCdRINszsm867lAA+T/Ei7qo=;
        b=O5+0NsdVucVX0eMaWRz/sCYJTlcjhX5UK9e6kEY3YXutPxM4uG+e0TKwZec1L3aJXS
         sczehxPDmYa79sUVNe5yLB8lBznKe/Lp4gBezzRPkzFvFX07LBk3wXWeHjit0TCM9j3q
         zQ4qCaHIfUwc8XBbChcyr2JZi3yxt1g6FX70bg4JYUZ1YI84660msR2SXNGuEIy7uM2S
         BTk53hotTTPnE5smyN/oTGrOorrr3OVJjZsOAd1m7i28NtdiFtTDIQ4aqGHeUUs08pF/
         CZQzVx0LGLeX6CY4UVmUfk5oryZaoQZgUeZ+VYxbiLF+xhv9EdPrFR688RcJIUi90h8m
         3Yug==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20161025;
        h=x-gm-message-state:mime-version:references:in-reply-to:from:date
         :message-id:subject:to:content-transfer-encoding;
        bh=vCsY5rvycDEqZVKTnBTuCdRINszsm867lAA+T/Ei7qo=;
        b=tU5xQNApKPPQfT1g8eqwwwmVuiSvIeD5Dp1nDwgD1TGyhs6tRdcHBpzNgiAYz+FHVf
         GJogfAi/SdLWKvcBijLUNokaLa0AmsYZUpD4A+oJUFIDWIwz5eRrE8i5SMRxgWc6PoG+
         xay42QCc7x3jIBQFPoIsCYBQ2YsNERaIKmtcmq5203Dz++YqJDb6edocRmHr8/RzU//c
         ur6kNNtCL50bIaVi6SvEytu89h7mZ+hqGq7uQBva4atV1kwirrYCagfJSRa1UkJPEUK1
         nBEakOWod30Q4cpaHahDgNsII1k9PffHW0H8YkGtGX2qcsTjejc7ad33ysrh0DIF58YV
         C/nA==
X-Gm-Message-State: AOAM532TivSNSAv5OuJuPRdi/wef4A8LDBOihY60Ilj/PC/HoV18Us9R
	q9ZN+n1eppsAB81JjsjymubTMqhegiZeLLtF3nK3Uw==
X-Google-Smtp-Source: ABdhPJzfhPmv/OWcBwub0+ySvAnzYF2y7ioGu0JCI4lDUrLyDSJraqbzrj7Eog2yrwh2LvrWgBBIbCciiotKGrwFWgg=
X-Received: by 2002:a92:9f06:: with SMTP id u6mr15479232ili.29.1593096769458;
 Thu, 25 Jun 2020 07:52:49 -0700 (PDT)
MIME-Version: 1.0
References: <CACsCw1OQDH61WMH2DWUCoJyG2dAfHsK6fWhCDWV5c6fJQaHJQQ@mail.gmail.com>
 <CADQ2Nw8eYNmumd6vxs-pg2-u6NhF2dTW8U591eDm2yd5fyNWjg@mail.gmail.com>
In-Reply-To: <CADQ2Nw8eYNmumd6vxs-pg2-u6NhF2dTW8U591eDm2yd5fyNWjg@mail.gmail.com>
From: Guillermo <gdiazhartusch@gmail.com>
Date: Thu, 25 Jun 2020 11:52:40 -0300
Message-ID: <CADQ2Nw9uHy8Ua2aGUB=pLf__FzV9Jamhrh29CrbaZk+dAAMuoQ@mail.gmail.com>
Subject: Re: Following log directories
To: Supervision <supervision@list.skarnet.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

El jue., 25 jun. 2020 a las 10:20, Guillermo escribi=C3=B3:
>
> El jue., 25 jun. 2020 a las 6:27, Carl Winb=C3=A4ck escribi=C3=B3:
>
> > 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.