Lines Matching +full:image +full:- +full:specific

7 .\" The Institute of Electrical and Electronics Engineers and The Open Group, have given us permission to reprint portions of their documentation. In the following statement, the phrase "this text" refers to portions of the system documentation. Portions of this text are reprinted and reproduced in electronic form in the Sun OS Reference Manual, from IEEE Std 1003.1, 2004 Edition, Standard for Information Technology -- Portable Operating System Interface (POSIX), The Open Group Base Specifications Issue 6, Copyright (C) 2001-2004 by the Institute of Electrical and Electronics Engineers, Inc and The Open Group. In the event of any discrepancy between these versions and the original IEEE and The Open Group Standard, the original IEEE and The Open Group Standard is the referee document. The original Standard can be obtained online at http://www.opengroup.org/unix/online.html.
10 .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing.  See the License for the specific language governing permissions and limitations under the License.
14 exec, execl, execle, execlp, execv, execve, execvp \- execute a file
56 image with a new process image. The new image is constructed from a regular,
57 executable file called the \fBnew process image file\fR. This file is either an
60 image is overlaid by the new process image.
69 .in -2
82 When a C-language program is executed as a result of this call, it is entered
83 as a C-language function call as follows:
89 .in -2
100 .in -2
110 The value of \fIargc\fR is non-negative, and if greater than 0, \fIargv\fR[0]
118 passed on to the new process image in the \fBmain()\fR arguments.
122 image file.
126 process image file. If the \fIfile\fR argument contains a slash character, it
130 shell. If the process image file is not a valid executable object file,
132 input to the shell. In this case, the shell becomes the new process image. The
138 null-terminated character strings. These strings constitute the argument list
139 available to the new process image. The list is terminated by a null pointer.
144 The \fIargv\fR argument is an array of character pointers to null-terminated
146 constitute the argument list available to the new process image. The value in
151 The \fIenvp\fR argument is an array of character pointers to null-terminated
152 strings. These strings constitute the environment for the new process image.
154 \fBexecv()\fR, \fBexecvp()\fR, and \fBexeclp()\fR, the C-language run-time
155 start-off routine places a pointer to the environment of the calling process in
157 environment of the calling process to the new process image.
161 environment lists is \fBARG_MAX\fR. It is implementation-dependent whether null
165 File descriptors open in the calling process image remain open in the new
166 process image, except for those whose close-on-exec flag \fBFD_CLOEXEC\fR is
173 stack and heap of the new process image are set to the default system page
177 Directory streams open in the calling process image are closed in the new
178 process image.
182 new process image is undefined. For the new process, the equivalent of:
188 .in -2
195 Signals set to the default action (\fBSIG_DFL\fR) in the calling process image
196 are set to the default action in the new process image (see \fBsignal\fR(3C)).
197 Signals set to be ignored (\fBSIG_IGN\fR) by the calling process image are set
198 to be ignored by the new process image. Signals set to be caught by the calling
199 process image are set to the default action in the new process image (see
209 The saved resource limits in the new process image are set to be a copy of the
214 process image file, then the effective user \fBID\fR and effective group
215 \fBID\fR are unchanged in the new process image. If the set-user-\fBID\fR mode
216 bit of the new process image file is set (see \fBchmod\fR(2)), the effective
217 user \fBID\fR of the new process image is set to the owner \fBID\fR of the new
218 process image file. Similarly, if the set-group-\fBID\fR mode bit of the new
219 process image file is set, the effective group \fBID\fR of the new process
220 image is set to the group \fBID\fR of the new process image file. The real user
221 \fBID\fR and real group \fBID\fR of the new process image remain the same as
222 those of the calling process image. The effective user ID and effective group
223 ID of the new process image are saved (as the saved set-user-ID and the saved
224 set-group-ID for use by \fBsetuid\fR(2).
242 The system attempts to set the privilege-aware state to non-PA both before
249 set-user-ID and set-group-ID bits will be honored when the process is being
254 Any shared memory segments attached to the calling process image will not be
255 attached to the new process image (see \fBshmop\fR(2)). Any mappings
258 rebuilt for the new process image. See \fBmmap\fR(2).
278 before replacing the current process image with the new process image.
294 process image created by the \fBexec\fR function be affected by the presence of
320 file-locks (see \fBfcntl\fR(2) and \fBlockf\fR(3C))
482 results in all threads being terminated and the new executable image being
488 function failed but was able to locate the \fBprocess image file\fR, whether
490 function succeed, the process image file is considered to have been opened with
496 consequence of replacing the process image.
499 The saved resource limits in the new process image are set to be a copy of the
504 If a function in the \fBexec\fR family returns to the calling process image, an
518 system-imposed limit of {\fBARG_MAX\fR} bytes. The argument list limit is sum
568 The new process image file has the appropriate permission and has a recognized
643 The new process image file has the appropriate access permission but is not in
666 The new process image requires more memory than is allowed by the hardware or
667 system-imposed by memory management constraints. See \fBbrk\fR(2).
676 The new process image file is a pure procedure (shared text) file that is
684 new process image is undefined, portable applications should not rely on their
709 MT-Level	See below.
716 The \fBexecle()\fR and \fBexecve()\fR fucntions are Async-Signal-Safe.
733 the program is executed when the real user \fBID\fR is super-user, then the
734 program has some of the powers of a super-user as well.