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: Fix typos in the fexecve description Date: Wed, 29 Apr 2020 09:24:03 +0000 (GMT) [thread overview] Message-ID: <20200429092403.6CB2E38930E6@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=2a8682ea3bf0f366a2d971ba6abdda4b2f7c3587 commit 2a8682ea3bf0f366a2d971ba6abdda4b2f7c3587 Author: Florian Weimer <fweimer@redhat.com> Date: Wed Apr 29 10:15:51 2020 +0200 manual: Fix typos in the fexecve description Reported by Michael Kerrisk. Diff: --- manual/process.texi | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/manual/process.texi b/manual/process.texi index b20ad26cbf..54e65f76c6 100644 --- a/manual/process.texi +++ b/manual/process.texi @@ -408,7 +408,7 @@ variable; see @ref{Environment Access}. @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 +This is similar to @code{execve}, but instead of identifying the program 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.
reply other threads:[~2020-04-29 9:24 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=20200429092403.6CB2E38930E6@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).