Lines Matching +full:function +full:- +full:group

1 .\"-
2 .\" SPDX-License-Identifier: BSD-3-Clause
55 .Bl -tag -width Ds
57 Each active process in the system is uniquely identified by a non-negative
70 .It Process Group
71 Each active process is a member of a process group that is identified by
72 a non-negative integer called the process group ID.
74 ID of the group leader.
84 group in the new session.
96 .It Terminal Process Group ID
100 the terminal process group ID to the ID of the process group.
104 .It Orphaned Process Group
105 A process group is considered to be
108 More precisely, a process group is orphaned
110 as the group,
111 but is in a different process group.
116 Not all members of an orphaned process group are necessarily orphaned
119 The process group of a session leader is orphaned by definition.
120 .It Real User ID and Real Group ID
128 integer corresponding to this distinguished group is termed
129 the real group ID.
131 All processes have a real user ID and real group ID.
134 .It Effective User Id, Effective Group Id, and Group Access List
136 the effective user ID, and the group access list.
137 The first member of the group access list is also known as the
138 effective group ID.
139 In POSIX.1, the group access list is known as the set of supplementary
140 group IDs, and it is unspecified whether the effective group ID is
143 The effective user ID and effective group ID are initially the
144 process's real user ID and real group ID respectively.
146 may be modified through execution of a set-user-ID or set-group-ID file
149 By convention, the effective group ID
150 .Pq the first member of the group access list
151 is duplicated, so that the execution of a set-group-ID program
154 group ID.
156 The group access list is a set of group IDs
160 .It Saved Set User ID and Saved Set Group ID
162 to the owner of the file if the file is set-user-ID, and the effective
163 group ID
164 .Pq first element of the group access list
165 is set to the group of the file if the file is set-group-ID.
166 The effective user ID of the process is then recorded as the saved set-user-ID,
167 and the effective group ID of the process is recorded as the saved set-group-ID.
169 or group ID after reverting to the real ID
171 In POSIX.1, the saved set-user-ID and saved set-group-ID are optional,
173 for the super-user.
174 .It Super-user
176 .Em super-user
197 These characters may be arbitrary eight-bit values,
217 .Dv NUL Ns -terminated
247 .Em dot-dot
250 dot-dot refers to its parent directory.
276 of the file, those users in the file's group, anyone else.
286 The process's effective user ID is that of the super-user.
287 Note that even the super-user cannot execute a non-executable file.
294 group ID matches the group ID
295 of the file, or the group ID of the file is in
296 the process's group access list,
297 and the group permissions allow the access.
299 Neither the effective user ID nor effective group ID
300 and group access list of the process
301 match the corresponding user ID and group ID of the file,
325 for a specific group of protocols.
330 .Bl -inset -compact
347 function returns a pointer to a field in the thread specific structure for
350 non-threaded processes,
359 .Pq usually -1
364 -1 and to take action accordingly.
376 .Bl -hang -width Ds
393 function.
427 function was executed by a process that had no existing or unwaited-for
434 or by system-imposed memory management constraints.
445 A block device operation was attempted on a non-block device or file.
454 .It Er 18 EXDEV Em "Cross-device link" .
459 function to a device,
461 trying to read a write-only device such as a printer.
471 function or a
486 A control function
512 .It Er 30 EROFS Em "Read-only file system" .
514 on a file system that was read-only at the time.
528 function.
530 A numerical result of the function was too large to fit in the
539 was attempted on a non-blocking object
542 An operation was attempted on a non-blocking object that already
544 .It Er 38 ENOTSOCK Em "Socket operation on non-socket" .
545 Self-explanatory.
692 A system-imposed limit on the number of simultaneous file
694 .It Er 78 ENOSYS Em "Function not implemented" .
712 A numerical result of the function was too large to be stored in the caller
717 While decoding a multibyte character the function came along an
723 A function or API is being abused in a way which could only be detected
724 at run-time.
743 An integrity check such as a check-hash or a cross-correlation failed.
750 filesystem or an in-kernel GEOM subsystem when they detect inconsistencies.