From: "Laurent Bercot" <ska-supervision@skarnet.org>
To: "Colin Booth" <colin@heliocat.net>, supervision@list.skarnet.org
Subject: Re: [s6-svperms] Handling service permissions at creation time.
Date: Mon, 15 Feb 2021 14:56:45 +0000 [thread overview]
Message-ID: <emd14d34b9-5cdf-4a75-9377-6d3addd47d9b@elzian> (raw)
In-Reply-To: <20210215122156.GA22296@cathexis.xen.prgmr.com>
>Services can fix their own permissions so if s6-rc is going to grow that
>functionality it should be in the generated run, not in some rarely used
>outboard helper service.
As answered on IRC, for ML completeness: no, because permissions should
be fixed when the supervisor starts, not when the service starts. So a
oneshot that runs right after the supervisors are started is the
correct solution.
--
Laurent
prev parent reply other threads:[~2021-02-15 14:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-25 16:50 [announce] skalibs-2.10.0.1, execline-2.7.0.1, s6-2.10.0.1 Laurent Bercot
2021-01-26 3:11 ` Alexis
2021-02-15 2:37 ` [s6-svperms] Handling service permissions at creation time eric vidal
2021-02-15 11:58 ` Laurent Bercot
2021-02-15 12:21 ` Colin Booth
2021-02-15 14:56 ` Laurent Bercot [this message]
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=emd14d34b9-5cdf-4a75-9377-6d3addd47d9b@elzian \
--to=ska-supervision@skarnet.org \
--cc=colin@heliocat.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).