From: Todd C. Miller <Todd.Miller@courtesan.com>
Date: Wed, 16 Jan 2002 00:22:21 +0000 (+0000)
Subject: Mention the "seteuid(0): Operation not permitted" problem here too
X-Git-Tag: SUDO_1_6_5~12
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=c12bb733b4948324c94a5f98ba295159466401d4;p=sudo

Mention the "seteuid(0): Operation not permitted" problem here too
just for good measure.
---

diff --git a/PORTING b/PORTING
index 861e0c03e..4c3ecdebd 100644
--- a/PORTING
+++ b/PORTING
@@ -21,6 +21,12 @@ the POSIX sysconf(2) it will be used instead of getdtablesize(2).
 ulimit(2) or getrlimit(2) can also be used on some OS's.  If all
 else fails you can use the value of NOFILE in <sys/param.h>.
 
+Also, some operating systems have a broken implementation of POSIX
+saved IDs.  If sudo prints the error message "seteuid(0): Operation
+not permitted" this means saved IDs are not implemented properly.
+You should run configure with the "--disable-saved-ids" option and
+rebuild sudo.
+
 Sudo tries to clear the environment of dangerous environment variables
 such as LD_* to prevent shared library spoofing.  If you are porting
 sudo to a new OS that has shared libraries you'll want to mask out