[2194] in Release_7.7_team
Fwd: A question about how groups get handled
daemon@ATHENA.MIT.EDU (Ted McCabe)
Mon Apr 3 15:58:29 2000
Mime-Version: 1.0
Message-Id: <v04220807b50ea66151af@[18.177.1.78]>
Date: Mon, 3 Apr 2000 15:57:48 -0400
To: release-team@mit.edu
From: Ted McCabe <ted@MIT.EDU>
Cc: tjm@mit.edu
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Tim,
I'm forwarding your question to release-team, since my understanding
of how the group list is created during login isn't complete.
--Ted
>Date: Mon, 3 Apr 2000 15:35:26 -0400
>To: ted@mit.edu
>From: Tim McGovern <tjm@MIT.EDU>
>Subject: A question about how groups get handled
>Cc: grouper@mit.edu
>
>Ted,
>
>Craig Counterman suggested you as an expert in how groups get handled in
>Athena.
>
>As you may know, we're working on a process which would create Moira lists
>for MIT subjects, the project known as Grouper or Class Participants Lists.
>One of the features of this process would be to create a group which could
>be used to control access to AFS course lockers, web pages, etc. It would
>be helpful to know how the /etc/groups file gets built on login. While the
>use of the /etc/groups file is irrelevant for AFS access control, we still
>do have some number of faculty and students who will depend on the proper
>setting of that file to access NFS servers, and the Grouper process will
>be putting users into new groups rather transparently.
>
>Any help you can provide in this regard would be helpful:
>
>1. On my Sun, it appears that the groups file contains 14 entries. Is this
>14 limit the same on all Athena platforms?
>
>2. In picking the 14 entries out of the 20 groups I'm in, how did it decide
>which 14 to use?
>
>3. Are there any particular characteristics of a list (hidden, visible,
>active, inactive) that would affect how it's handled for the /etc/groups
>file?
>
>If there are other resources/information, please pass them along so that we
>can make sure that the right thing happens.
>
>Tim
>
