Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!sun-barr!decwrl!pyramid!voder!wlbr!WLV.IMSD.CONTEL.COM!sms
From: sms@WLV.IMSD.CONTEL.COM (Steven M. Schultz)
Newsgroups: comp.unix.wizards
Subject: Re: BSD file system
Message-ID: <38688@wlbr.IMSD.CONTEL.COM>
Date: 20 Oct 89 12:33:11 GMT
References: <1344@accuvax.nwu.edu> <20258@mimsy.umd.edu>
Sender: news@wlbr.IMSD.CONTEL.COM
Reply-To: sms@WLV.IMSD.CONTEL.COM.UUCP (Steven M. Schultz)
Distribution: na
Organization: Contel Federal Systems
Lines: 20

>In article <20258@mimsy.umd.edu> chris@mimsy.umd.edu (Chris Torek) writes:
>>In article <1344@accuvax.nwu.edu> rico@dehn. (Rico Tudor) writes:
>>	(3) What purpose is served by taking the group ID of a newly
>>		created file from the parent directory, rather than the
>>		process?
>
>Given that `the process' may be in up to 8 (4.2BSD) or 16 (4.3BSD)
>groups simultaneously, there is no single correct choice based on
>the process alone, hence the parent directory rule.

	Another way of looking at the multi-group capability is that
	a process has a main/primary group - the one listed in the 
	password file and multiple secondary groups as determined by
	the group file.  It makes sense to me to use the primary
	group for purposes of file ownership.   Directories such as /tmp
	typically are owned by groups of which users are not members, this
	has led to surprises at least once for me.

	Steven M. Schultz
	sms@wlv.imsd.contel.com