From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Egmont Koblinger <egmont-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
linux-man <linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: getlogin(3): mention loginuid
Date: Wed, 18 May 2016 22:36:37 +0200 [thread overview]
Message-ID: <8ee6ef8b-c976-0410-e525-42689b4bdf94@gmail.com> (raw)
In-Reply-To: <CAGWcZkJFZZQgCAs4JnnGBj1jSh9aYdBiDUhRA+yj1Wx64H0xXA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On 04/23/2016 11:00 PM, Egmont Koblinger wrote:
> Hi,
>
> I just got to know about /proc/self/loginuid, as well as getlogin(3)
> referring to this file prior to utmp, by browsing this bug:
> https://bugzilla.redhat.com/show_bug.cgi?id=1328947 (esp. comments
> 13-17 are relevant).
>
> getlogin(3)'s manual page does not mention this at all. (And, for the
> record, neither does proc(5), it has a FIXME comment about it).
>
> Could you please fill in this gap?
Hello Egmont,
Can you provide some information about this field? If not a patch
to the man page, then at least some descriptive text?
Thanks,
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
next prev parent reply other threads:[~2016-05-18 20:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-23 21:00 getlogin(3): mention loginuid Egmont Koblinger
[not found] ` <CAGWcZkJFZZQgCAs4JnnGBj1jSh9aYdBiDUhRA+yj1Wx64H0xXA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-05-18 20:36 ` Michael Kerrisk (man-pages) [this message]
[not found] ` <8ee6ef8b-c976-0410-e525-42689b4bdf94-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-05-18 20:48 ` Egmont Koblinger
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=8ee6ef8b-c976-0410-e525-42689b4bdf94@gmail.com \
--to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=egmont-Re5JQEeQqe8AvxtiuMwx3w@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.