Lines Matching refs:its

13 The effective user and group IDs of a process collectively form its
15 Normally, a process inherits its persona from the parent process, but
16 under special circumstances a process can change its persona and thus
17 change its access permissions.
32 				 its user and/or group IDs.
112 its permission to access files, see @ref{Access Permission}.
129 its user and/or group IDs is the @code{login} program.  When
130 @code{login} starts running, its user ID is @code{root}.  Its job is to
133 user and group IDs as well as its persona.  But this is a special case.)
144 change its effective user or group ID to match that of the resource.
153 the game program wants to update this file, it can change its effective
171 program to change its persona is that it has been set up in advance to
180 group ID} equal to the group ID of the file, and its effective group ID
184 change its effective ID to its real ID and back to its file ID.
322 provided that the process is allowed to change its effective user ID.  A
323 privileged process (effective user ID zero) can change its effective
325 can change its effective user ID to its real user ID or to its file user
326 ID.  Otherwise, a process may not change its effective user ID at all.
406 @var{newgid}, provided that the process is allowed to change its group
408 change its effective group ID to any value; if it isn't, but it has a
409 file group ID, then it may change to its real group ID or file group ID;
410 otherwise it may not change its effective group ID.
412 Note that a process is only privileged if its effective @emph{user} ID
593 A typical setuid program does not need its special access all of the
598 accomplish this with @code{seteuid}.  When the game program starts, its
599 real user ID is @code{jdoe}, its effective user ID is @code{games}, and
600 its saved user ID is also @code{games}.  The program should record both
623 file user ID remains @code{games}, so the program can always set its
638 game program has just started, and its real user ID is @code{jdoe} while
639 its effective user ID is @code{games}.  In this state, the game can
659 Here's an example showing how to set up a program that changes its
664 itself.  The program assumes that its executable file will be installed
703 /* @r{Restore the effective UID to its original value.} */
802 minimizing its consequences when it does occur: