xref: /freebsd-14.2/lib/libc/sys/execve.2 (revision 0eec3684)
1.\" Copyright (c) 1980, 1991, 1993
2.\"	The Regents of the University of California.  All rights reserved.
3.\"
4.\" Redistribution and use in source and binary forms, with or without
5.\" modification, are permitted provided that the following conditions
6.\" are met:
7.\" 1. Redistributions of source code must retain the above copyright
8.\"    notice, this list of conditions and the following disclaimer.
9.\" 2. Redistributions in binary form must reproduce the above copyright
10.\"    notice, this list of conditions and the following disclaimer in the
11.\"    documentation and/or other materials provided with the distribution.
12.\" 3. All advertising materials mentioning features or use of this software
13.\"    must display the following acknowledgement:
14.\"	This product includes software developed by the University of
15.\"	California, Berkeley and its contributors.
16.\" 4. Neither the name of the University nor the names of its contributors
17.\"    may be used to endorse or promote products derived from this software
18.\"    without specific prior written permission.
19.\"
20.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
21.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
22.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
23.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
24.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
25.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
26.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
27.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
28.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
29.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
30.\" SUCH DAMAGE.
31.\"
32.\"     @(#)execve.2	8.3 (Berkeley) 1/24/94
33.\"
34.Dd January 24, 1994
35.Dt EXECVE 2
36.Os BSD 4
37.Sh NAME
38.Nm execve
39.Nd execute a file
40.Sh SYNOPSIS
41.Fd #include <unistd.h>
42.Ft int
43.Fn execve "const char *path" "char *const argv[]" "char *const envp[]"
44.Sh DESCRIPTION
45.Fn Execve
46transforms the calling process into a new process.
47The new process is constructed from an ordinary file,
48whose name is pointed to by
49.Fa path ,
50called the
51.Em new process file .
52This file is either an executable object file,
53or a file of data for an interpreter.
54An executable object file consists of an identifying header,
55followed by pages of data representing the initial program (text)
56and initialized data pages.  Additional pages may be specified
57by the header to be initialized with zero data;  see
58.Xr a.out 5 .
59.Pp
60An interpreter file begins with a line of the form:
61.Pp
62.Bd -filled -offset indent -compact
63.Sy \&#!
64.Em interpreter
65.Bq Em arg
66.Ed
67.Pp
68When an interpreter file is
69.Fn execve Ap d ,
70the system
71.Fn execve Ap s
72runs the specified
73.Em interpreter .
74If the optional
75.Em arg
76is specified, it becomes the first argument to the
77.Em interpreter ,
78and the name of the originally
79.Fn execve Ap d
80file becomes the second argument;
81otherwise, the name of the originally
82.Fn execve Ap d
83file becomes the first argument.  The original arguments are shifted over to
84become the subsequent arguments.  The zeroth argument, normally the name of the
85.Fn execve Ap d
86file, is left unchanged.
87.Pp
88The argument
89.Fa argv
90is a pointer to a null-terminated array of
91character pointers to null-terminated character strings.
92These strings construct the argument list to be made available to the new
93process.  At least one argument must be present in
94the array; by custom, the first element should be
95the name of the executed program (for example, the last component of
96.Fa path ) .
97.Pp
98The argument
99.Fa envp
100is also a pointer to a null-terminated array of
101character pointers to null-terminated strings.
102A pointer to this array is normally stored in the global variable
103.Va environ.
104These strings pass information to the
105new process that is not directly an argument to the command (see
106.Xr environ 7 ) .
107.Pp
108File descriptors open in the calling process image remain open in
109the new process image, except for those for which the close-on-exec
110flag is set (see
111.Xr close 2
112and
113.Xr fcntl 2 ) .
114Descriptors that remain open are unaffected by
115.Fn execve .
116.Pp
117Signals set to be ignored in the calling process are set to be ignored in
118the
119new process. Signals which are set to be caught in the calling process image
120are set to default action in the new process image.
121Blocked signals remain blocked regardless of changes to the signal action.
122The signal stack is reset to be undefined (see
123.Xr sigaction 2
124for more information).
125.Pp
126If the set-user-ID mode bit of the new process image file is set
127(see
128.Xr chmod 2 ) ,
129the effective user ID of the new process image is set to the owner ID
130of the new process image file.
131If the set-group-ID mode bit of the new process image file is set,
132the effective group ID of the new process image is set to the group ID
133of the new process image file.
134(The effective group ID is the first element of the group list.)
135The real user ID, real group ID and
136other group IDs of the new process image remain the same as the calling
137process image.
138After any set-user-ID and set-group-ID processing,
139the effective user ID is recorded as the saved set-user-ID,
140and the effective group ID is recorded as the saved set-group-ID.
141These values may be used in changing the effective IDs later (see
142.Xr setuid 2 ) .
143.Pp
144The new process also inherits the following attributes from
145the calling process:
146.Pp
147.Bl -column parent_process_ID -offset indent -compact
148.It process ID Ta see Xr getpid 2
149.It parent process ID Ta see Xr getppid 2
150.It process group ID Ta see Xr getpgrp 2
151.It access groups Ta see Xr getgroups 2
152.It working directory Ta see Xr chdir 2
153.It root directory Ta see Xr chroot 2
154.It control terminal Ta see Xr termios 4
155.It resource usages Ta see Xr getrusage 2
156.It interval timers Ta see Xr getitimer 2
157.It resource limits Ta see Xr getrlimit 2
158.It file mode mask Ta see Xr umask 2
159.It signal mask Ta see Xr sigvec 2 ,
160.Xr sigsetmask 2
161.El
162.Pp
163When a program is executed as a result of an
164.Fn execve
165call, it is entered as follows:
166.Bd -literal -offset indent
167main(argc, argv, envp)
168int argc;
169char **argv, **envp;
170.Ed
171.Pp
172where
173.Fa argc
174is the number of elements in
175.Fa argv
176(the ``arg count'')
177and
178.Fa argv
179points to the array of character pointers
180to the arguments themselves.
181.Sh RETURN VALUES
182As the
183.Fn execve
184function overlays the current process image
185with a new process image the successful call
186has no process to return to.
187If
188.Fn execve
189does return to the calling process an error has occurred; the
190return value will be -1 and the global variable
191.Va errno
192is set to indicate the error.
193.Sh ERRORS
194.Fn Execve
195will fail and return to the calling process if:
196.Bl -tag -width [ENAMETOOLONG]
197.It Bq Er ENOTDIR
198A component of the path prefix is not a directory.
199.It Bq Er EINVAL
200The pathname contains a character with the high-order bit set.
201.It Bq Er ENAMETOOLONG
202A component of a pathname exceeded 255 characters,
203or an entire path name exceeded 1023 characters.
204.It Bq Er ENOENT
205The new process file does not exist.
206.It Bq Er ELOOP
207Too many symbolic links were encountered in translating the pathname.
208.It Bq Er EACCES
209Search permission is denied for a component of the path prefix.
210.It Bq Er EACCES
211The new process file is not an ordinary file.
212.It Bq Er EACCES
213The new process file mode denies execute permission.
214.It Bq Er ENOEXEC
215The new process file has the appropriate access
216permission, but has an invalid magic number in its header.
217.It Bq Er ETXTBSY
218The new process file is a pure procedure (shared text)
219file that is currently open for writing or reading by some process.
220.It Bq Er ENOMEM
221The new process requires more virtual memory than
222is allowed by the imposed maximum
223.Pq Xr getrlimit 2 .
224.It Bq Er E2BIG
225The number of bytes in the new process's argument list
226is larger than the system-imposed limit.
227The limit in the system as released is 20480 bytes
228.Pf ( Dv NCARGS
229in
230.Ao Pa sys/param.h Ac .
231.It Bq Er EFAULT
232The new process file is not as long as indicated by
233the size values in its header.
234.It Bq Er EFAULT
235.Fa Path ,
236.Fa argv ,
237or
238.Fa envp
239point
240to an illegal address.
241.It Bq Er EIO
242An I/O error occurred while reading from the file system.
243.El
244.Sh CAVEAT
245If a program is
246.Em setuid
247to a non-super-user, but is executed when
248the real
249.Em uid
250is ``root'', then the program has some of the powers
251of a super-user as well.
252.Sh SEE ALSO
253.Xr exit 2 ,
254.Xr fork 2 ,
255.Xr execl 3 ,
256.Xr environ 7
257.Sh HISTORY
258The
259.Nm
260function call appeared in
261.Bx 4.2 .
262