seteuid.2: Note unstandardized behavior for effective ID

PSOIX.1 doesn't require that the effective ID can be changed
to the same value it currently has (a no-op). The man page
should note this, since some other implementations
don't permit it.

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk 2009-10-17 07:06:46 +02:00
parent 70ccce1140
commit b033d60f29
1 changed files with 10 additions and 1 deletions

View File

@ -24,7 +24,7 @@
.\" Modified, 27 May 2004, Michael Kerrisk <mtk.manpages@gmail.com>
.\" Added notes on capability requirements
.\"
.TH SETEUID 2 2007-07-26 "Linux" "Linux Programmer's Manual"
.TH SETEUID 2 2009-10-17 "Linux" "Linux Programmer's Manual"
.SH NAME
seteuid, setegid \- set effective user or group ID
.SH SYNOPSIS
@ -103,6 +103,15 @@ Under glibc 2.1 and later it is equivalent to
and hence does not change the saved set-user-ID.
Similar remarks hold for
.BR setegid ().
According to POSIX.1,
.BR seteuid ()
.RB ( setegid ())
need not permit
.I euid
.RI ( egid )
to be the same value as the current effective user (group) ID,
and some implementations do not permit this.
.SH "SEE ALSO"
.BR geteuid (2),
.BR setresuid (2),