From: Kir Kolyshkin <kolyshkin@gmail.com>
To: mtk.manpages@gmail.com
Cc: linux-man@vger.kernel.org, Kir Kolyshkin <kolyshkin@gmail.com>
Subject: [PATCH] proc(5): ffix
Date: Fri, 13 Mar 2020 09:14:58 -0700 [thread overview]
Message-ID: <20200313161458.412515-1-kolyshkin@gmail.com> (raw)
Mark some literal strings with bold.
Mark some variable strings with italic.
Remove some unneeded R from .BR, .IR etc.
Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
---
man5/proc.5 | 45 +++++++++++++++++++++++++++++----------------
1 file changed, 29 insertions(+), 16 deletions(-)
diff --git a/man5/proc.5 b/man5/proc.5
index a5dbad702..58129cdcf 100644
--- a/man5/proc.5
+++ b/man5/proc.5
@@ -131,7 +131,7 @@ but it hides a process's UID and GID,
which could otherwise be learned by employing
.BR stat (2)
on a
-.IR /proc/[pid]
+.I /proc/[pid]
directory.
This greatly complicates an attacker's task of gathering
information about running processes (e.g., discovering whether
@@ -144,11 +144,11 @@ whether other users are running any program at all, and so on).
.\" commit 0499680a42141d86417a8fbaa8c8db806bea1201
Specifies the ID of a group whose members are authorized to
learn process information otherwise prohibited by
-.BR hidepid
+.B hidepid
(i.e., users in this group behave as though
.I /proc
was mounted with
-.IR hidepid=0 ).
+.BR hidepid=0 ).
This group should be used instead of approaches such as putting
nonroot users into the
.BR sudoers (5)
@@ -1465,16 +1465,20 @@ mount options: per-mount options (see
.BR mount (2)).
.TP
(7)
-optional fields: zero or more fields of the form "tag[:value]"; see below.
+optional fields: zero or more fields of the form
+.IR tag [: value ];
+see below.
.TP
(8)
separator: the end of the optional fields is marked by a single hyphen.
.TP
(9)
-filesystem type: the filesystem type in the form "type[.subtype]".
+filesystem type: the filesystem type in the form
+.IR type [. subtype ].
.TP
(10)
-mount source: filesystem-specific information or "none".
+mount source: filesystem-specific information or
+.BR none .
.TP
(11)
super options: per-superblock options (see
@@ -1482,11 +1486,11 @@ super options: per-superblock options (see
.RE
.IP
Currently, the possible optional fields are
-.IR shared ,
-.IR master ,
-.IR propagate_from ,
+.BR shared ,
+.BR master ,
+.BR propagate_from ,
and
-.IR unbindable .
+.BR unbindable .
See
.BR mount_namespaces (7)
for a description of these fields.
@@ -1540,7 +1544,9 @@ The fields in each line are:
.TP 5
(1)
The name of the mounted device
-(or "nodevice" if there is no corresponding device).
+(or
+.B nodevice
+if there is no corresponding device).
.TP
(2)
The mount point within the filesystem tree.
@@ -2856,11 +2862,18 @@ Valid only for timers that notify via a signal.
.I notify
The part before the slash specifies the mechanism
that this timer uses to deliver notifications,
-and is one of "thread", "signal", or "none".
-Immediately following the slash is either the string "tid" for timers
-with
+and is one of
+.BR thread ,
+.BR signal ,
+or
+.BR none .
+Immediately following the slash is either the string
+.B tid
+for timers with
.B SIGEV_THREAD_ID
-notification, or "pid" for timers that notify by other mechanisms.
+notification, or
+.B pid
+for timers that notify by other mechanisms.
Following the "." is the PID of the process
(or the kernel thread ID of the thread) that will be delivered
a signal if the timer delivers notifications via a signal.
@@ -2868,7 +2881,7 @@ a signal if the timer delivers notifications via a signal.
.I ClockID
This field identifies the clock that the timer uses for measuring time.
For most clocks, this is a number that matches one of the user-space
-.BR CLOCK_*
+.B CLOCK_*
constants exposed via
.IR <time.h> .
.B CLOCK_PROCESS_CPUTIME_ID
--
2.24.1
reply other threads:[~2020-03-13 16:15 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=20200313161458.412515-1-kolyshkin@gmail.com \
--to=kolyshkin@gmail.com \
--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).