Most people actually want exec(3) (or one of its aliases); the minutiae are a separate, rarer, concern, and execve(2) hijacks man execve from all the other exec(3) aliases (similarly to exec(1posix), but it's at least obvious in that case that you got the wrong page) Reported-in: https://twitter.com/NireBryce/status/1529538043039850499 Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@xxxxxxxxxxxxxxxxxx> --- man2/execve.2 | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/man2/execve.2 b/man2/execve.2 index 0d9582492..28c175132 100644 --- a/man2/execve.2 +++ b/man2/execve.2 @@ -80,6 +80,14 @@ The .I envp array must be terminated by a NULL pointer. .PP +This manual page describes the Linux system call in detail; +for an overview of the nomenclature and the many, often preferable, +standardised variants of this function provided by libc, +including ones that search the +.B PATH +environment variable, see +.BR exec (3). +.PP The argument vector and environment can be accessed by the new program's main function, when it is defined as: .PP -- 2.30.2
Attachment:
signature.asc
Description: PGP signature
