Xref: utzoo comp.bugs.sys5:1162 comp.unix.wizards:18686
Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!gem.mps.ohio-state.edu!apple!agate!shelby!portia!forel!karish
From: karish@forel.stanford.edu (Chuck Karish)
Newsgroups: comp.bugs.sys5,comp.unix.wizards
Subject: Re: SysVR3.2 Setpgrp behaviour
Summary: It gets worse
Message-ID: <5843@portia.Stanford.EDU>
Date: 14 Oct 89 17:41:06 GMT
References: <1970@oid.UUCP> <1273@virtech.UUCP> <253664A4.20995@ateng.com>
Sender: USENET News System <news@Portia.stanford.edu>
Reply-To: karish@forel.stanford.edu (Chuck Karish)
Followup-To: comp.bugs.sys5
Organization: Mindcraft, Inc.
Lines: 9

In article <253664A4.20995@ateng.com> chip@ateng.com (Chip Salzenberg) wrote:

>Personally, I think this whole "setpgrp does two jobs" is a grody hack.

How about setsid()?  It does three jobs: setpgrp()'s two, plus
making the caller the foreground process.

	Chuck Karish		karish@mindcraft.com
	(415) 493-9000		karish@forel.stanford.edu