supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Charles Duffy <cduffy@spamcop.net>
Subject: chpst and secondary groups (runit-1.2.3)
Date: Mon, 15 Aug 2005 16:01:28 -0500	[thread overview]
Message-ID: <pan.2005.08.15.21.01.28.953741@spamcop.net> (raw)

I have a service which needs serial port access, meaning it needs access
to a secondary group (its primary one is set differently for Good Reasons).

Right now I'm using chpst (from runit) to set the uid and gid for this
process -- but chpst doesn't set secondary groups. This is, for obvious
reasons, problematic.

Any suggested workarounds? Using ACLs for the relevant permissions is
distinctly unpleasant. 



             reply	other threads:[~2005-08-15 21:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-15 21:01 Charles Duffy [this message]
2005-08-15 21:09 ` Paul Jarc

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=pan.2005.08.15.21.01.28.953741@spamcop.net \
    --to=cduffy@spamcop.net \
    /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).