linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Simone Piccardi <piccardi@truelite.it>
Cc: mtk.manpages@gmail.com, linux-man@vger.kernel.org
Subject: Re: fececve man page
Date: Fri, 13 Sep 2019 14:36:56 +0200	[thread overview]
Message-ID: <1a7418f3-8c05-ff91-1635-5c448ea304ec@gmail.com> (raw)
In-Reply-To: <044d4f18-fe49-7e25-ddae-844ce6a50b7a@truelite.it>

On 8/21/19 6:44 PM, Simone Piccardi wrote:
> 
> In http://man7.org/linux/man-pages/man3/fexecve.3.html in the reported 
> errors there are only EINVAL and ENOSYS but in the BUGS section is cited 
> also ENOENT (I suppose coming from execveat) for trying to use a script.
> 
> Furthermore I think that ENOSYS should be cited as present only when 
> fexecve is not implemented using execveat.

Thanks, Simone. I've applied the following diff.

Cheers,

Michael

diff --git a/man3/fexecve.3 b/man3/fexecve.3
index 25cf049dc..73b086881 100644
--- a/man3/fexecve.3
+++ b/man3/fexecve.3
@@ -86,8 +86,18 @@ is NULL, or
 .I envp
 is NULL.
 .TP
+.B ENOENT
+The close-on-exec flag is set on
+.IR fd ,
+and
+.I fd
+refers to a script.
+See BUGS.
+.TP
 .B ENOSYS
-The
+The kernel does not provide the
+.BR execveat (2)
+system call, and the
 .I /proc
 filesystem could not be accessed.
 .SH VERSIONS



-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/

      reply	other threads:[~2019-09-13 12:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-21 16:44 fececve man page Simone Piccardi
2019-09-13 12:36 ` Michael Kerrisk (man-pages) [this message]

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=1a7418f3-8c05-ff91-1635-5c448ea304ec@gmail.com \
    --to=mtk.manpages@gmail.com \
    --cc=linux-man@vger.kernel.org \
    --cc=piccardi@truelite.it \
    /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: link
Be 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 NNTP newsgroup(s).