Examples of using Execve in English and their translations into Japanese
{-}
-
Colloquial
-
Ecclesiastic
-
Computer
-
Programming
For details, see execve(2).
The execve() system call appeared in BSD 4.2.
Saved set IDs may be changed, as described in execve(2).
Execve() executes the program pointed to by filename.
The functions described in this manual page are front-ends for execve(2).
If execve() does return to the calling process an error has occurred;
Similarly, a DOS file may be found to be"executable," but the execve(2) call will still fail.
On success, execve() does not return, on error -1 is returned, and errno is set appropriately.
Mitigation and preventionTo prevent exposure: Use fork, execve, and pipes to control process execution completely.
Both the second field and any command specified with''window='' will be split into words and executed using execve(2).
If a new process is then to be run using execve(2), the process would normally inherit these descriptors.
Signals to the parent arrive after the child releases the parent's memory(i.e., after the child terminates or calls execve(2)).
If a new process is then to be run using execve(2), the process would normally inherit these descriptors.
Execve() does not return on success, and the text, data, bss, and stack of the calling process are overwritten by that of the program loaded.
If your program must spawn processes,use only the execve(), execv(), or execl() calls, and use them with great care.
In most cases where execve() fails, control returns to the original executable image, and the caller of execve() can then handle the error.
When sudo runs a command, it calls fork(2), sets up the execution environment as described above,and calls the execve system call in the child process.
In most cases where execve() fails, control returns to the original executable image, and the caller of execve() can then handle the error.
A process can overlay itself with the memory image of another program, passing to the newly created image a set of parameters,using the system call execve.
The execve(2) system call reinstates the default action for all signals which were caught and resets all signals to be caught on the user stack.
These IDs are used in set-user-ID and set-group-ID programs to save a copy of the corresponding effective IDs that were set when the program was executed(see execve(2)).
If the shell is not given a-f option, the shell hashes the names in these directories into an internal table so that it will try an execve(2) in only a directory where there is a possibility that the command resides there.
These IDs are used in set-user-ID and set-group-ID programs to save a copy of the corre- sponding effective IDs that were set when the program was executed(see execve(2)).
If the resource limit was not still exceeded at the time of the execve() call(because other processes belonging to this real UID terminated between the set*uid() call and the execve() call), then the execve() call succeeds and the kernel clears the PF_NPROC_EXCEEDED process flag.
Most of the descriptors can be rearranged with dup2(2) or deleted with close() before the execve(2) is attempted, but since some of these descriptors may still be needed should the execve(2) fail, it is necessary to arrange for them to be closed when the execve(2) succeeds.
The upshot of the above rules, combined with the capabilities transformations described above, is that when a process execve(2)s a set-user-ID-root program, or when a process with an effective UID of 0 execve(2)s a program, it gains all capabilities in its permitted and effective capability sets, except those masked out by the capability bounding set.