public inbox for glibc-cvs@sourceware.org help / color / mirror / Atom feed
From: Florian Weimer <fw@sourceware.org> To: glibc-cvs@sourceware.org Subject: [glibc] manual: Document the fexecve function Date: Mon, 27 Apr 2020 10:44:43 +0000 (GMT) [thread overview] Message-ID: <20200427104443.5F04E3986032@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=6771af1123d55e08450ccf4553dd0d674b7f099b commit 6771af1123d55e08450ccf4553dd0d674b7f099b Author: Florian Weimer <fweimer@redhat.com> Date: Mon Apr 27 11:38:28 2020 +0200 manual: Document the fexecve function Diff: --- manual/process.texi | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/manual/process.texi b/manual/process.texi index 5728bde2cb..b20ad26cbf 100644 --- a/manual/process.texi +++ b/manual/process.texi @@ -405,6 +405,19 @@ be an array of strings in the same format as for the @code{environ} variable; see @ref{Environment Access}. @end deftypefun +@deftypefun int fexecve (int @var{fd}, char *const @var{argv}@t{[]}, char *const @var{env}@t{[]}) +@standards{POSIX.1, unistd.h} +@safety{@prelim{}@mtsafe{}@assafe{}@acsafe{}} +This is similar to @code{execve}, but instead identifying the progam +executable by its pathname, the file descriptor @var{fd} is used. The +descriptor must have been opened with the @code{O_RDONLY} flag or (on +Linux) the @code{O_PATH} flag. + +On Linux, @code{fexecve} can fail with an error of @code{ENOSYS} if +@file{/proc} has not been mounted and the kernel lacks support for the +underlying @code{execveat} system call. +@end deftypefun + @deftypefun int execle (const char *@var{filename}, const char *@var{arg0}, @dots{}, char *const @var{env}@t{[]}) @standards{POSIX.1, unistd.h} @safety{@prelim{}@mtsafe{}@asunsafe{@ascuheap{}}@acunsafe{@acsmem{}}}
reply other threads:[~2020-04-27 10:44 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20200427104443.5F04E3986032@sourceware.org \ --to=fw@sourceware.org \ --cc=glibc-cvs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).