All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Patrick Donnelly <batrick-dP08NitdTj1Wk0Htik3J/w@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
	linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: proc(5) fdinfo should mention O_CLOEXEC may be set in file flags
Date: Tue, 8 Mar 2016 20:33:35 +0100	[thread overview]
Message-ID: <56DF290F.4070104@gmail.com> (raw)
In-Reply-To: <CACh33FqAXhMsJoFszxNkLG+MWoP6eXKjfaDb1XoDGGcXhdgZFA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

Hello Patrick

On 03/07/2016 08:51 PM, Patrick Donnelly wrote:
> The man page says this
> 
> "The flags field is an octal number that displays the file access mode
> and file  status  flags  (see  open(2))."
> 
> flags may also include the file descriptor flags (F_GETFD). (Although
> there is only the O_CLOEXEC flag and that is explicitly included [1])
> 
> [1] https://github.com/torvalds/linux/blob/master/fs/proc/fd.c#L41-L43

Thanks. I added this detail.

Cheers,

Michael


-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2016-03-08 19:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-07 19:51 proc(5) fdinfo should mention O_CLOEXEC may be set in file flags Patrick Donnelly
     [not found] ` <CACh33FqAXhMsJoFszxNkLG+MWoP6eXKjfaDb1XoDGGcXhdgZFA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-03-08 19:33   ` 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=56DF290F.4070104@gmail.com \
    --to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=batrick-dP08NitdTj1Wk0Htik3J/w@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.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: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.