From mboxrd@z Thu Jan 1 00:00:00 1970 From: Russ Allbery Subject: Re: Re: [PATCH] in-core AFS multiplexor and PAG support Date: Tue, 13 May 2003 14:46:27 -0700 Sender: openafs-devel-admin@openafs.org Message-ID: References: <1052840663.463.64.camel@dhcp22.swansea.linux.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Linus Torvalds , David Howells , Linux Kernel Mailing List , linux-fsdevel@vger.kernel.org, openafs-devel@openafs.org Return-path: To: Alan Cox In-Reply-To: <1052840663.463.64.camel@dhcp22.swansea.linux.org.uk> (Alan Cox's message of "13 May 2003 16:44:24 +0100") Errors-To: openafs-devel-admin@openafs.org List-Help: List-Post: List-Subscribe: , List-Unsubscribe: , List-Archive: List-Id: linux-fsdevel.vger.kernel.org Alan Cox writes: > How does AFS currently handle this, can two logins of the same user have > seperate PAGs ? Yes. In fact, that's the default situation and it requires some work to get two logins of the same user into the same PAG. AFS currently handles PAGs by creating "random" high-numbered groups and putting the user into them, and then associating the token with that group in the kernel. One could debate whether it's best to put a user into the same PAG as their other logins by default, but it's imperative that a user be able to create a separate PAG when they wish to (so, for example, they can acquire separate credentials in that new PAG without affecting the credentials and PAG for their other running processes). -- Russ Allbery (rra@stanford.edu)