From: Jeff <sysinit@yandex.com>
To: init <supervision@list.skarnet.org>
Subject: Re: chpst -u and supplementary groups
Date: Wed, 28 Aug 2019 01:44:36 +0200 [thread overview]
Message-ID: <4779971566949476@vla4-d1c3bcedfacb.qloud-c.yandex.net> (raw)
> Apparently everyone re-implementing daemontools does something like
> this. So that brings me back to my original question:
> is there consensus that the historical behaviour is a bug?
no, this is no bug.
> Or are there valid use cases?
most of the time one does not want the subprocess to run under
additional GIDs, so that is a sane default behaviour.
obviously there should be an option that makes "chpst" add all
supplementary GIDs the UID belongs to, though
(when this is desired by the user).
would not be too much work to add such a commandline option to it.
next reply other threads:[~2019-08-27 23:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-27 23:44 Jeff [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-08-19 12:08 Jan Braun
2019-08-19 19:33 ` Steve Litt
2019-08-19 22:06 ` Bougy Man
2019-08-20 7:25 ` Jonathan de Boyne Pollard
2019-08-20 10:04 ` Jan Braun
2019-08-20 18:21 ` Laurent Bercot
2019-08-21 3:50 ` Jan Braun
2019-08-20 18:25 ` Cameron Nemo
2019-08-21 3:22 ` Jan Braun
2019-08-21 22:26 ` Steve Litt
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=4779971566949476@vla4-d1c3bcedfacb.qloud-c.yandex.net \
--to=sysinit@yandex.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).