Path: utzoo!censor!geac!lethe!yunexus!ists!helios.physics.utoronto.ca!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!usc!zaphod.mps.ohio-state.edu!uwm.edu!bionet!ames!vsi1!daver!tscs!tct!chip
From: chip@tct.uucp (Chip Salzenberg)
Newsgroups: comp.unix.sysv386
Subject: Re: system(3) behaviour under Esix rev. D
Message-ID: <27C93418.F26@tct.uucp>
Date: 25 Feb 91 15:58:16 GMT
Article-I.D.: tct.27C93418.F26
References: <1991Feb17.214252.27336@metro.ucc.su.OZ.AU> <868@mecky.UUCP>
Organization: Teltronics/TCT, Sarasota, FL
Lines: 10

According to walter@mecky.UUCP (Walter Mecky):
>I can not speak for ESIX, but in my system (SCO UNIX) this is a
>(not documented) fact:
>
>	sh resets the effective uid back to the real 
>	uid if they are different and the EUID != 0.
>

SCO support has confirmed that /bin/sh doesn't like EUID and UID
differing, and attempts to "correct" the matter.  Double bleh.