From: Lucas Werkmeister <mail@lucaswerkmeister.de>
To: Michael Kerrisk <mtk.manpages@gmail.com>
Cc: linux-man@vger.kernel.org, Lucas Werkmeister <mail@lucaswerkmeister.de>
Subject: [PATCH] proc.5: Add /proc/[pid]/loginuid
Date: Mon, 14 Oct 2019 01:32:53 +0200 [thread overview]
Message-ID: <20191013233253.110036-1-mail@lucaswerkmeister.de> (raw)
Signed-off-by: Lucas Werkmeister <mail@lucaswerkmeister.de>
---
Notes:
On my system, this file is used by logname(1), but I decided against
mentioning the command, since it’s an indirect relation at best (via
getlogin(3)) that’s not mentioned in other documentation either.
man5/proc.5 | 20 +++++++++++++++++---
1 file changed, 17 insertions(+), 3 deletions(-)
diff --git a/man5/proc.5 b/man5/proc.5
index dd05db6c6..25a971afc 100644
--- a/man5/proc.5
+++ b/man5/proc.5
@@ -1190,9 +1190,23 @@ this file is protected to allow reading only by the real UID of the process.
Since Linux 2.6.36,
.\" commit 3036e7b490bf7878c6dae952eec5fb87b1106589
this file is readable by all users on the system.
-.\" FIXME Describe /proc/[pid]/loginuid
-.\" Added in 2.6.11; updating requires CAP_AUDIT_CONTROL
-.\" CONFIG_AUDITSYSCALL
+.TP
+.IR /proc/[pid]/loginuid " (since Linux 2.6.11)"
+This file contains the login user ID of the process,
+which is typically set by
+.BR pam_loginuid (8)
+during the login process and not influenced by later user changes
+such as through commands like
+.BR su (1)
+or
+.BR sudo (8).
+A process must be privileged
+.RB ( CAP_AUDIT_CONTROL )
+to update this file.
+This file is present only if the kernel was configured with
+.BR CONFIG_AUDIT " (since Linux 5.1),"
+previously
+.BR CONFIG_AUDITSYSCALL .
.TP
.IR /proc/[pid]/map_files/ " (since kernel 3.3)
.\" commit 640708a2cff7f81e246243b0073c66e6ece7e53e
--
2.23.0
reply other threads:[~2019-10-13 23:40 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=20191013233253.110036-1-mail@lucaswerkmeister.de \
--to=mail@lucaswerkmeister.de \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
/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).