From: "Laurent Bercot" <ska-supervision@skarnet.org>
To: Guillermo <gdiazhartusch@gmail.com>,
"supervision@list.skarnet.org" <supervision@list.skarnet.org>
Subject: Re: s6-supervise: use of nosetsid
Date: Fri, 04 Dec 2020 06:29:59 +0000 [thread overview]
Message-ID: <em0c4fd79e-0adb-4690-84f9-bc87a73ae95f@elzian> (raw)
In-Reply-To: <CADQ2Nw9Dtq7qFVoja01RCrJ0z8duBce+Q2qV6y3MDBMWCmq5SA@mail.gmail.com>
>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?
Yes. That's why it's the "advanced" solution over just leaking a fd
for /dev/tty.
> Anyway, nosetsid + /dev/tty is still the simplest implementation, I
>have to admit.
The more I think about it, the more I see any use of nosetsid as
incorrect. Implementing SIGINT handling for s6-supervise requires
jumping through serious hoops if the nosetsid function still exists, and
the point of my current work on s6 is to get things simpler, not more
complex.
I'm leaning more and more in the direction of removing nosetsid, which
is why I want to help people find other ways to accomplish what they're
currently doing with it.
--
Laurent
next prev parent reply other threads:[~2020-12-04 6:30 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
2020-12-04 6:29 ` Laurent Bercot [this message]
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=em0c4fd79e-0adb-4690-84f9-bc87a73ae95f@elzian \
--to=ska-supervision@skarnet.org \
--cc=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).