Update for new error messages from set_perms()

diff --git a/PORTING b/PORTING
index 4c3ecdebd805d98fdcf1e9359815c585186ea3fe..1d42ebd6bac64c581f4ebb5b9a14e31c40bb34e6 100644 (file)
--- a/PORTING
+++ b/PORTING
@@ -22,10 +22,10 @@ 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.
+saved IDs.  If sudo prints the error message "seteuid(0) failed,
+your operating system may have broken POSIX saved ID support" 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