man-pages/man3/exec.3

215 lines
6.7 KiB
Groff
Raw Normal View History

2004-11-03 13:51:07 +00:00
.\" Copyright (c) 1991 The Regents of the University of California.
.\" All rights reserved.
.\"
.\" Redistribution and use in source and binary forms, with or without
.\" modification, are permitted provided that the following conditions
.\" are met:
.\" 1. Redistributions of source code must retain the above copyright
.\" notice, this list of conditions and the following disclaimer.
.\" 2. Redistributions in binary form must reproduce the above copyright
.\" notice, this list of conditions and the following disclaimer in the
.\" documentation and/or other materials provided with the distribution.
.\" 3. All advertising materials mentioning features or use of this software
.\" must display the following acknowledgement:
.\" This product includes software developed by the University of
.\" California, Berkeley and its contributors.
.\" 4. Neither the name of the University nor the names of its contributors
.\" may be used to endorse or promote products derived from this software
.\" without specific prior written permission.
.\"
.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
.\" SUCH DAMAGE.
.\"
.\" @(#)exec.3 6.4 (Berkeley) 4/19/91
.\"
.\" Converted for Linux, Mon Nov 29 11:12:48 1993, faith@cs.unc.edu
.\" Updated more for Linux, Tue Jul 15 11:54:18 1997, pacman@cqc.com
2007-09-20 06:52:22 +00:00
.\" Modified, 24 Jun 2004, Michael Kerrisk <mtk.manpages@gmail.com>
2004-11-03 13:51:07 +00:00
.\" Added note on casting NULL
.\"
.TH EXEC 3 2008-08-20 "GNU" "Linux Programmer's Manual"
2004-11-03 13:51:07 +00:00
.SH NAME
execl, execlp, execle, execv, execvp \- execute a file
.SH SYNOPSIS
.B #include <unistd.h>
.sp
.B extern char **environ;
.sp
.BI "int execl(const char *" path ", const char *" arg ", ...);"
.br
.BI "int execlp(const char *" file ", const char *" arg ", ...);"
.br
2006-03-05 22:59:17 +00:00
.BI "int execle(const char *" path ", const char *" arg ,
.br
.BI " ..., char * const " envp "[]);"
2004-11-03 13:51:07 +00:00
.br
.BI "int execv(const char *" path ", char *const " argv "[]);"
.br
.BI "int execvp(const char *" file ", char *const " argv "[]);"
.SH DESCRIPTION
The
.BR exec ()
2004-11-03 13:51:07 +00:00
family of functions replaces the current process image with a new process
image.
2008-07-09 09:51:47 +00:00
The functions described in this manual page are front-ends for
2004-11-03 13:51:07 +00:00
.BR execve (2).
(See the manual page for
.BR execve (2)
2008-07-09 09:51:47 +00:00
for further details about the replacement of the current process image.)
2004-11-03 13:51:07 +00:00
.PP
The initial argument for these functions is the pathname of a file which is
to be executed.
.PP
The
.I "const char *arg"
and subsequent ellipses in the
.BR execl (),
.BR execlp (),
2004-11-03 13:51:07 +00:00
and
.BR execle ()
2004-11-03 13:51:07 +00:00
functions can be thought of as
.IR arg0 ,
.IR arg1 ,
\&...,
.IR argn .
Together they describe a list of one or more pointers to null-terminated
strings that represent the argument list available to the executed program.
2006-02-12 22:15:41 +00:00
The first argument, by convention, should point to the filename associated
with the file being executed.
The list of arguments
2004-11-03 13:51:07 +00:00
.I must
2005-11-02 13:55:25 +00:00
be terminated by a NULL
2004-11-03 13:51:07 +00:00
pointer, and, since these are variadic functions, this pointer must be cast
2008-07-09 09:51:47 +00:00
.IR "(char *) NULL" .
2004-11-03 13:51:07 +00:00
.PP
The
.BR execv ()
2004-11-03 13:51:07 +00:00
and
.BR execvp ()
2004-11-03 13:51:07 +00:00
functions provide an array of pointers to null-terminated strings that
represent the argument list available to the new program.
The first argument, by convention, should point to the filename
associated with the file being executed.
The array of pointers
2004-11-03 13:51:07 +00:00
.I must
2005-11-02 13:55:25 +00:00
be terminated by a NULL pointer.
2004-11-03 13:51:07 +00:00
.PP
The
.BR execle ()
2004-11-03 13:51:07 +00:00
function also specifies the environment of the executed process by following
2005-11-02 13:55:25 +00:00
the NULL
pointer that terminates the list of arguments in the argument list or the
pointer to the
.I argv
array with an additional argument.
This additional
argument is an array of pointers to null-terminated strings and
2004-11-03 13:51:07 +00:00
.I must
be terminated by a NULL pointer.
2005-11-02 13:55:25 +00:00
The other functions take the environment for the new process
2004-11-03 13:51:07 +00:00
image from the external variable
.I environ
in the current process.
.SS Special semantics for execlp() and execvp()
2004-11-03 13:51:07 +00:00
.PP
The functions
.BR execlp ()
2004-11-03 13:51:07 +00:00
and
.BR execvp ()
2004-11-03 13:51:07 +00:00
will duplicate the actions of the shell in searching for an executable file
if the specified filename does not contain a slash (/) character.
The search path is the path specified in the environment by the
2004-11-03 13:51:07 +00:00
.B PATH
variable.
If this variable isn't specified, the default path
2007-12-16 14:08:46 +00:00
":/bin:/usr/bin" is used.
In addition, certain
2004-11-03 13:51:07 +00:00
errors are treated specially.
.PP
If permission is denied for a file (the attempted
2007-05-21 17:45:30 +00:00
.BR execve (2)
failed with the error
2004-11-03 13:51:07 +00:00
.BR EACCES ),
these functions will continue searching the rest of the search path.
If no other file is found, however,
they will return with the global variable
2004-11-03 13:51:07 +00:00
.I errno
set to
.BR EACCES .
.PP
If the header of a file isn't recognized (the attempted
2007-05-21 17:45:30 +00:00
.BR execve (2)
failed with the error
2004-11-03 13:51:07 +00:00
.BR ENOEXEC ),
2007-06-21 22:55:04 +00:00
these functions will execute the shell
.RI ( /bin/sh )
with the path of the file as its first argument.
(If this attempt fails, no further searching is done.)
2004-11-03 13:51:07 +00:00
.SH "RETURN VALUE"
If any of the
.BR exec ()
functions returns, an error will have occurred.
The return value is \-1,
2004-11-03 13:51:07 +00:00
and the global variable
.I errno
will be set to indicate the error.
.SH ERRORS
All of these functions may fail and set
.I errno
for any of the errors specified for the library function
.BR execve (2).
.SH "CONFORMING TO"
POSIX.1-2001.
.SH NOTES
2004-11-03 13:51:07 +00:00
On some other systems the default path (used when the environment
does not contain the variable \fBPATH\fR) has the current working
directory listed after
.I /bin
and
.IR /usr/bin ,
as an anti-Trojan-horse measure.
Linux uses here the
2004-11-03 13:51:07 +00:00
traditional "current directory first" default path.
.PP
The behavior of
.BR execlp ()
2004-11-03 13:51:07 +00:00
and
.BR execvp ()
2004-11-03 13:51:07 +00:00
when errors occur while attempting to execute the file is historic
practice, but has not traditionally been documented and is not specified by
the POSIX standard.
BSD (and possibly other systems) do an automatic
2007-06-22 19:42:52 +00:00
sleep and retry if
.B ETXTBSY
is encountered.
Linux treats it as a hard
2004-11-03 13:51:07 +00:00
error and returns immediately.
.PP
Traditionally, the functions
.BR execlp ()
2004-11-03 13:51:07 +00:00
and
.BR execvp ()
2004-11-03 13:51:07 +00:00
ignored all errors except for the ones described above and
.B ENOMEM
and
.BR E2BIG ,
upon which they returned.
They now return if any error other than the ones
2004-11-03 13:51:07 +00:00
described above occurs.
2007-05-16 18:25:50 +00:00
.SH "SEE ALSO"
.BR sh (1),
.BR execve (2),
.BR fork (2),
.BR ptrace (2),
.BR fexecve (3),
.BR environ (7)