From: Guillermo <gdiazhartusch@gmail.com>
To: "supervision@list.skarnet.org" <supervision@list.skarnet.org>
Subject: Re: s6-supervise: use of nosetsid
Date: Thu, 3 Dec 2020 22:46:26 -0300 [thread overview]
Message-ID: <CADQ2Nw9Dtq7qFVoja01RCrJ0z8duBce+Q2qV6y3MDBMWCmq5SA@mail.gmail.com> (raw)
In-Reply-To: <em599c31f9-f497-4f3d-83f9-363cd9fa220e@elzian>
El jue, 3 dic 2020 a las 18:34, Laurent Bercot escribió:
>
> So, can you juggle fds to avoid nosetsid, or can't you do the same
> thing without it?
This particular use of nosetsid can probably be implemented in some
other way. I did think about having supervision tree processes inherit
a FD for the shell's terminal from s6-svscan, and also about using an
s6-fdholderd process, and having supervision tree processes retrieve
the FD from it. Although I haven't tested either yet.
It seems I missed the addition of s6-svscan's -X option; I saw it one
day in the output of 'ps' on a VM that was using s6-linux-init, didn't
recognize it, but then forgot to look up what it did :P But I would
have to 'tag' messages in some way, so that the catch-all logger
recognizes them and sends them to the terminal, right?
Anyway, nosetsid + /dev/tty is still the simplest implementation, I
have to admit.
G.
next prev parent reply other threads:[~2020-12-04 1:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-03 16:46 Laurent Bercot
2020-12-03 17:09 ` Casper Ti. Vector
[not found] ` <X8kbtfETM/jWuG1O@caspervector>
2020-12-03 17:21 ` Laurent Bercot
2020-12-04 6:45 ` Casper Ti. Vector
2020-12-03 19:53 ` Steve Litt
2020-12-03 19:56 ` Guillermo
2020-12-03 21:34 ` Laurent Bercot
2020-12-04 1:46 ` Guillermo [this message]
2020-12-04 6:29 ` Laurent Bercot
2020-12-03 21:25 ` eric vidal
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=CADQ2Nw9Dtq7qFVoja01RCrJ0z8duBce+Q2qV6y3MDBMWCmq5SA@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).