From: Paul Furness <paul.furness@vil.ite.mee.com>
To: Jamie Harris <jamie@jharris.homeip.net>
Cc: linux-admin@vger.kernel.org
Subject: Re: Recursive groups anyone?
Date: 14 Sep 2002 08:39:42 +0100 [thread overview]
Message-ID: <1031989182.24112.12.camel@Zebra> (raw)
In-Reply-To: <9566.194.82.103.138.1031933445.squirrel@jharris.homeip.net>
Thanks.
Hmm, I'll have to do with scripts by the look of things.
On Fri, 2002-09-13 at 17:10, Jamie Harris wrote:
>
> Are you changing their primary
> group of adding them to additional groups? How are you checking their
> membership? Usinggetent etc or something else?
>
It was mainly for secondary group changes. I was looking at it very
simply: I wanted to be able to give someone rights to a group, and them
be able to immediately access the file (eg using cat).
But I can't do that, since (as GC explained) the group memberships are
attached to the process - so you can't change them externally. I guess I
_could_ probably write a script to update the running process (provided
it's a shell) but it's only a minor inconvenience - people are usually
ok about logging out when they have asked for group membership to be
changes.
> You might want to look into storing your group information
> in another way rather than tradition groups files under NIS. LDAP might
> provide you with whatyou're looking for as I imagine you would just query the directory for group
> membership.
That _might_ be easier to manage, possibly, but I don't now think it'll
make any difference to the log out/in thing. Like I say, that's less
important.
Thanks.
P.
--
Paul Furness
Systems Manager
2+2=5 for extremely large values of 2.
next prev parent reply other threads:[~2002-09-14 7:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-13 11:17 Recursive groups anyone? Paul Furness
2002-09-13 14:53 ` Glynn Clements
2002-09-14 7:53 ` Paul Furness
2002-09-14 14:24 ` Glynn Clements
2002-09-13 16:10 ` Jamie Harris
2002-09-14 7:39 ` Paul Furness [this message]
2002-09-14 14:31 ` Glynn Clements
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=1031989182.24112.12.camel@Zebra \
--to=paul.furness@vil.ite.mee.com \
--cc=jamie@jharris.homeip.net \
--cc=linux-admin@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.