From owner-freebsd-arch Tue Jan 16 12:10:45 2001 Delivered-To: freebsd-arch@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id EBFE437B401 for ; Tue, 16 Jan 2001 12:10:27 -0800 (PST) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.9.3/8.9.3) with ESMTP id PAA322366; Tue, 16 Jan 2001 15:10:24 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <20010116161703.H364@ringworld.oblivion.bg> References: <20010116161703.H364@ringworld.oblivion.bg> Date: Tue, 16 Jan 2001 15:10:22 -0500 To: Peter Pentchev , arch@FreeBSD.ORG From: Garance A Drosihn Subject: Re: no newgroup/newgrp in FreeBSD? Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 4:17 PM +0200 1/16/01, Peter Pentchev wrote: >PS. And yes, I've heard before that FreeBSD is still quite far > from SUSv2 compliance; still, I had to write this for a friend > with some very weird shell/web hosting requirements, who did > not want to change his existing scripts' modus operandi.. If your friend is worried about SingleUnixSpec V2, he should read this quote from the description of newgrp in that specification: The newgrp command is intended only for use from an interactive terminal. It does not offer a useful interface for the support of applications. The exit status of newgrp is generally inapplicable. If newgrp is used in a script, in most cases it will successfully invoke a new shell and the rest of the original shell script will be bypassed when the new shell exits. So while it might be debated whether FreeBSD should have any newgrp command at all, the specification makes it clear that your friend should not be using it in any script. Thus, tell your friend to change his scripts, "in order to comply with SUSv2". -- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message