Lines Matching +full:protect +full:- +full:exec

16 .\" Standard for Information Technology -- Portable Operating System
18 .\" Copyright (C) 2001-2004 by the Institute of Electrical and Electronics
50 fork, fork1, forkall, forkx, forkallx \- create a new process
103 open file descriptors (except those marked close-on-fork, see discussion below)
109 close-on-exec flags (see \fBexec\fR(2))
128 set-user-ID mode bit
134 set-group-ID mode bit
164 process group \fBID\fR -- memory mappings (see \fBmmap\fR(2))
246 Scheduling priority and any per-process scheduling parameters that are specific
273 file descriptors that were marked with the close-on-fork flag, \fBFD_CLOFORK\fR
365 calling thread is replicated in the child process. This is the POSIX-specified
371 library. When linked with \fB-lthread\fR (Solaris Threads) but not linked with
372 \fB-lpthread\fR (POSIX Threads), \fBfork()\fR was the same as \fBforkall()\fR.
373 When linked with \fB-lpthread\fR, whether or not also linked with
374 \fB-lthread\fR, \fBfork()\fR was the same as \fBfork1()\fR.
377 Prior to Solaris 10, either \fB-lthread\fR or \fB-lpthread\fR was required for
380 interfaces.  Applications that require replicate-all fork semantics must call
384 consisting of a bitwise inclusive-OR of zero or more of the following flags,
406 Do not allow wait-for-multiple-pids by the parent, as in \fBwait()\fR,
422 \fBexec\fR(2) functions, there is a possibility of deadlock occurring in the
427 \fBfork1()\fR, or \fBforkx()\fR. See  "MT-Level" on the \fBattributes\fR(7)
431 The \fBpthread_atfork()\fR mechanism is used to protect the locks that
438 Async-Signal-Safe (see \fBattributes\fR(7)). This cannot be made to happen with
446 Async-Signal-Safe operations until such time as one of the \fBexec\fR(2)
513 MT-Level	Async-Signal-Safe.
522 \fBalarm\fR(2), \fBexec\fR(2), \fBexit\fR(2), \fBfcntl\fR(2),