NAME

execv, execve − execute a file

SYNOPSIS

execv(name, argv)
char ∗name, ∗argv[];

execve(name, argv, envp)
char ∗name, ∗argv[], ∗envp[];

DESCRIPTION

Exec in all its forms overlays the calling process with the named file, then transfers to the entry point of the core image of the file.  There can be no return from a successful exec; the calling core image is lost. 

Descriptors remain open across exec unless explicit arrangement has been made; see ioctl(2). Ignored/held signals remain ignored/held across these calls, but signals that are caught (see signal(2)) are reset to their default values.

Each user has a real user ID and group ID and an effective user ID and group ID.  The real ID identifies the person using the system; the effective ID determines his access privileges.  Exec changes the effective user and group ID to the owner of the executed file if the file has the “set-user-ID” or “set-group-ID” modes.  The real user ID is not affected. 

The name argument is a pointer to the name of the file to be executed.  The pointers argv[0], argv[1] ... address null-terminated strings. Conventionally argv[0] is the name of the file. The last argument string must be followed by a 0 pointer.

When a C program is executed, it is called as follows:

main(argc, argv, envp)
int argc;
char ∗∗argv, ∗∗envp;

where argc is the argument count and argv is an array of character pointers to the arguments themselves.  As indicated, argc is conventionally at least one and the first member of the array points to a string containing the name of the file. 

Argv is directly usable in another execv because argv[argc] is 0.

Envp is a pointer to an array of strings that constitute the environment of the process.  Each string consists of a name, an “=”, and a null-terminated value.  The array of pointers is terminated by a null pointer.  The shell sh(1) passes an environment entry for each global shell variable defined when the program is called. See environ(5) for some conventionally used names. The C run-time start-off routine places a copy of envp in the global cell environ, which is used by execv to pass the environment to any subprograms executed by the current program. 

To aid execution of command files of various programs, if the first two characters of the executable file are ’#!’ then execv attempts to read a pathname from the executable file and use that program as the command files command interpreter. For example, the following command file sequence would be used to begin a csh script:

#! /bin/csh
# This shell script computes the checksum on /dev/foobar
#
...

A single parameter may be passed the interpreter, specified after the name of the interpreter; its length and the length of the name of the interpreter combined must not exceed 32 characters.  The space (or tab) following the ’#!’ is mandatory, and the pathname must be explicit (no paths are searched). 

SEE ALSO

fork(2), execl(3), environ(5), csh(1)

DIAGNOSTICS

If the file cannot be found, if it is not executable, if it does not start with a valid magic number (see a.out(5)), if maximum memory is exceeded, or if the arguments require too much space, a return constitutes the diagnostic; the return value is −1. Even for the super-user, at least one of the execute-permission bits must be set for a file to be executed. a 0 word is left at the very top of memory.

ASSEMBLER

On a VAX-11, the stack begins at 0x7ffff000 and grows towards lower numbered addresses.  After an exec, the layout of data on the stack is as follows.

 ap →
 fp →
 sp →.long nargs
.long arg0
...
.long argn
.long 0
.long env0
...
.long envn
.long 0
 arg0:.byte "arg0\0"
...
 envn:.byte "envn\0"
.long 0

Sun System Release 0.3  —  11/26/82