From: "Carl Winbäck" <c@tunnel53.net>
To: supervision@list.skarnet.org
Subject: Re: Logging in a web server context
Date: Sat, 13 Jun 2020 14:40:38 +0200 [thread overview]
Message-ID: <CACsCw1PmE1eTqUa1kGGhbKbs=jDj=jmzj=-uVsGyjsqRSDMa2g@mail.gmail.com> (raw)
In-Reply-To: <20200613113240.GA7301@CasperVector>
On Sat, 13 Jun 2020 at 13:59, Casper Ti. Vector <caspervector@gmail.com> wrote:
> > I gather from it that what I want is currently not possible without
> > s6-rc. Is that correct?
>
> I do not think so :) In a nutshell, your service needs to connect its
> stdout and stderr to a pair of different loggers; that can be done by
> fd-holding and chainloading, and is how s6-rc internally implements its
> piping (well, funneling) mechanism. However, s6-rc only connects the
> stdout, so the fd-holder needs an amount of additional configuration
> whether you use s6-rc or not; that amount will be a bit big without
> s6-rc, but it is surely doable and even scriptable.
Aha! Implementing such a mechanism (outside of s6-rc) could be an
interesting exercise.
However, I believe that the proposals Jan posted would be sufficient
for my needs.
next prev parent reply other threads:[~2020-06-13 12:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-13 8:41 Carl Winbäck
2020-06-13 10:04 ` Casper Ti. Vector
2020-06-13 10:50 ` Carl Winbäck
2020-06-13 11:32 ` Casper Ti. Vector
2020-06-13 12:40 ` Carl Winbäck [this message]
2020-06-13 10:59 ` Jan Braun
2020-06-13 11:17 ` Carl Winbäck
2020-06-13 12:42 ` Laurent Bercot
2020-06-13 12:53 ` Laurent Bercot
2020-06-14 12:06 ` Carl Winbäck
2020-06-14 12:02 ` Carl Winbäck
[not found] ` <20200613100522.jvixsd6fnokz3fh2@bstg>
2020-06-13 12:17 ` Carl Winbäck
2020-06-13 12:30 ` Carl Winbäck
2020-06-13 18:51 ` Steve Litt
2020-06-13 19:29 ` yianiris
2020-06-15 4:19 ` Colin Booth
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='CACsCw1PmE1eTqUa1kGGhbKbs=jDj=jmzj=-uVsGyjsqRSDMa2g@mail.gmail.com' \
--to=c@tunnel53.net \
--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).