Newsgroups: comp.sys.sgi
Path: utzoo!utgpu!adam
From: adam@gpu.utcs.utoronto.ca (Adam R. Iles)
Subject: Re: multgrps
Message-ID: <1990Nov27.022811.10329@gpu.utcs.utoronto.ca>
Organization: UTCS Public Access
References: <9011230236.7542@godzilla.cgl.rmit.oz.au> <1990Nov26.214307.10874@odin.corp.sgi.com>
Date: Tue, 27 Nov 90 02:28:11 GMT

In article <1990Nov26.214307.10874@odin.corp.sgi.com> bowen@wanda.SGI.COM (Jerre Bowen) writes:
>In article <9011230236.7542@godzilla.cgl.rmit.oz.au>,
>mg@GODZILLA.CGL.RMIT.OZ.AU (Mike Gigante) writes:
>> 
>> Any other suggestions? Is there any intention of making multiple group
>> support the default?
>
>	Meanwhile, we activate them on a per-user basis by adding 'exec /bin/multgrps'
>as the LAST LINE of the .login file.

I did this when we first got 3.3.1 up on our 340.  There are two important
points that I think should be made about this.

	1) The shell will no longer know that it is a login shell.
		Thus the logout and login commands will not work and
		the ~/.logout file will not be run.

	2) If the user issues the command 'exec login' to log into another
		account ALL of his multiple groups will STILL be active
		on the account that he logs into.  Not too secure eh? :-(

I will not put the 'exec /bin/multgrps' command in another users .login
because of these problems.  I hope that the next release will fix these
problems.


-- 
Adam R. Iles:	adam@epas.utoronto.ca

	Cut back on CO2 emissions -- Stop breathing :-)