From owner-freebsd-hackers  Fri May 31 03:52:31 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id DAA04924
          for hackers-outgoing; Fri, 31 May 1996 03:52:31 -0700 (PDT)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id DAA04909
          for <freebsd-hackers@freebsd.org>; Fri, 31 May 1996 03:52:24 -0700 (PDT)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id UAA00009; Fri, 31 May 1996 20:46:10 +1000
Date: Fri, 31 May 1996 20:46:10 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199605311046.UAA00009@godzilla.zeta.org.au>
To: freebsd-hackers@freebsd.org, j@uriah.heep.sax.de
Subject: Re: newgrp(1)
Cc: kuku@gilberto.physik.rwth-aachen.de
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>needed there.  Anyway, SysV semantics are to create a file with the
>primary group ownership.  BSD semantics is to create a file inheriting
>the group ownership from the parent directory -- so who cares for the
>primary group at all?

Programs that create temporary files in $TMPDIR (usually with the wrong
group) and move the result to a file in another file system.  If the
program is run by root, then the result ends up with the wrong group
ownership.  Otherwise the chown to set the group fails and the result
ends up with the right ownership.  An annoying warning message if printed
about the failure if the program isn't sloppy.

Bruce