Use a single-font-style macro (".B", ".I") for a single argument.
Remove unneeded quotation marks (").
Signed-off-by: Bjarni Ingi Gislason <bjarniig@xxxxxxxxx>
---
man7/icmp.7 | 2 +-
man7/inode.7 | 40 ++++++++++++++++++++--------------------
man7/inotify.7 | 40 ++++++++++++++++++++--------------------
man7/ip.7 | 22 +++++++++++-----------
4 files changed, 52 insertions(+), 52 deletions(-)
diff --git a/man7/icmp.7 b/man7/icmp.7
index 3722839cb..5e607e448 100644
--- a/man7/icmp.7
+++ b/man7/icmp.7
@@ -114,7 +114,7 @@ These packets are sent when a packet arrives with an invalid IP header.
.IR icmp_ratelimit " (integer; default: 1000; since Linux 2.4.10)"
.\" The following taken from 2.6.28-rc4 Documentation/networking/ip-sysctl.txt
Limit the maximum rates for sending ICMP packets whose type matches
-.IR icmp_ratemask
+.I icmp_ratemask
(see below) to specific targets.
0 to disable any limiting,
otherwise the minimum space between responses in milliseconds.
diff --git a/man7/inode.7 b/man7/inode.7
index 56886b9b4..71d0f1e4f 100644
--- a/man7/inode.7
+++ b/man7/inode.7
@@ -167,7 +167,7 @@ and related information in
.BR mount (2).)
In addition, the atime timestamp
is not updated if a file is opened with the
-.BR O_NOATIME
+.B O_NOATIME
flag; see
.BR open (2).
.TP
@@ -233,7 +233,7 @@ bits corresponding to the mask
(see below) as the
.IR "file type" ,
the 12 bits corresponding to the mask 07777 as the
-.IR "file mode bits"
+.I file mode bits
and the least significant 9 bits (0777) as the
.IR "file permission bits" .
.PP
@@ -305,42 +305,42 @@ if (S_ISREG(sb.st_mode)) {
.PP
The definitions of most of the above file type test macros
are provided if any of the following feature test macros is defined:
-.BR _BSD_SOURCE
+.B _BSD_SOURCE
(in glibc 2.19 and earlier),
-.BR _SVID_SOURCE
+.B _SVID_SOURCE
(in glibc 2.19 and earlier),
or
-.BR _DEFAULT_SOURCE
+.B _DEFAULT_SOURCE
(in glibc 2.20 and later).
In addition, definitions of all of the above macros except
-.BR S_IFSOCK
+.B S_IFSOCK
and
.BR S_ISSOCK ()
are provided if
-.BR _XOPEN_SOURCE
+.B _XOPEN_SOURCE
is defined.
.PP
The definition of
-.BR S_IFSOCK
+.B S_IFSOCK
can also be exposed either by defining
-.BR _XOPEN_SOURCE
+.B _XOPEN_SOURCE
with a value of 500 or greater or (since glibc 2.24) by defining both
-.BR _XOPEN_SOURCE
+.B _XOPEN_SOURCE
and
.BR _XOPEN_SOURCE_EXTENDED .
.PP
The definition of
.BR S_ISSOCK ()
is exposed if any of the following feature test macros is defined:
-.BR _BSD_SOURCE
+.B _BSD_SOURCE
(in glibc 2.19 and earlier),
-.BR _DEFAULT_SOURCE
+.B _DEFAULT_SOURCE
(in glibc 2.20 and later),
-.BR _XOPEN_SOURCE
+.B _XOPEN_SOURCE
with a value of 500 or greater,
-.BR _POSIX_C_SOURCE
+.B _POSIX_C_SOURCE
with a value of 200112L or greater, or (since glibc 2.24) by defining both
-.BR _XOPEN_SOURCE
+.B _XOPEN_SOURCE
and
.BR _XOPEN_SOURCE_EXTENDED .
.PP
@@ -396,13 +396,13 @@ of the file, by the owner of the directory, and by a privileged
process.
.SH CONFORMING TO
If you need to obtain the definition of the
-.IR blkcnt_t
+.I blkcnt_t
or
-.IR blksize_t
+.I blksize_t
types from
.IR <sys/stat.h> ,
then define
-.BR _XOPEN_SOURCE
+.B _XOPEN_SOURCE
with the value 500 or greater (before including
.I any
header files).
@@ -422,7 +422,7 @@ the macros
.BR S_ISDIR (),
and so on.
The
-.BR S_IF*
+.B S_IF*
constants are present in POSIX.1-2001 and later.
.PP
The
@@ -450,7 +450,7 @@ For example, the value 0 is returned for many files under the
.I /proc
directory,
while various files under
-.IR /sys
+.I /sys
report a size of 4096 bytes, even though the file content is smaller.
For such files, one should simply try to read as many bytes as possible
(and append \(aq\e0\(aq to the returned buffer
diff --git a/man7/inotify.7 b/man7/inotify.7
index 85c05a9bc..8fa34eee0 100644
--- a/man7/inotify.7
+++ b/man7/inotify.7
@@ -46,7 +46,7 @@ The more recent
is like
.BR inotify_init (2),
but has a
-.IR flags
+.I flags
argument that provides access to some extra functionality.
.IP *
.BR inotify_add_watch (2)
@@ -306,11 +306,11 @@ argument when calling
Two additional convenience macros are defined:
.RS 4
.TP
-.BR IN_MOVE
+.B IN_MOVE
Equates to
.BR "IN_MOVED_FROM | IN_MOVED_TO" .
.TP
-.BR IN_CLOSE
+.B IN_CLOSE
Equates to
.BR "IN_CLOSE_WRITE | IN_CLOSE_NOWRITE" .
.RE
@@ -398,7 +398,7 @@ event will subsequently be generated for the watch descriptor.
Suppose an application is watching the directory
.I dir
and the file
-.IR dir/myfile
+.I dir/myfile
for all events.
The examples below show some events that will be generated
for these two objects.
@@ -458,7 +458,7 @@ link("dir1/myfile", "dir2/new");
Generates an
.B IN_ATTRIB
event for
-.IR myfile
+.I myfile
and an
.B IN_CREATE
event for
@@ -487,9 +487,9 @@ value.
.RE
.PP
Suppose that
-.IR dir1/xx
+.I dir1/xx
and
-.IR dir2/yy
+.I dir2/yy
are (the only) links to the same file, and an application is watching
.IR dir1 ,
.IR dir2 ,
@@ -502,9 +502,9 @@ the following events:
.TP
unlink("dir2/yy");
Generates an
-.BR IN_ATTRIB
+.B IN_ATTRIB
event for
-.IR xx
+.I xx
(because its link count changes)
and an
.B IN_DELETE
@@ -516,17 +516,17 @@ Generates
.BR IN_ATTRIB ,
.BR IN_DELETE_SELF ,
and
-.BR IN_IGNORED
+.B IN_IGNORED
events for
.IR xx ,
and an
-.BR IN_DELETE
+.B IN_DELETE
event for
.IR dir1 .
.RE
.PP
Suppose an application is watching the directory
-.IR dir
+.I dir
and (the empty) directory
.IR dir/subdir .
The following examples show some events that may be generated.
@@ -605,11 +605,11 @@ The
structure (described in
.BR sigaction (2))
that is passed to the signal handler has the following fields set:
-.IR si_fd
+.I si_fd
is set to the inotify file descriptor number;
-.IR si_signo
+.I si_signo
is set to the signal number;
-.IR si_code
+.I si_code
is set to
.BR POLL_IN ;
and
@@ -639,7 +639,7 @@ correct order on the inotify file descriptor.
The set of watch descriptors that is being monitored via
an inotify file descriptor can be viewed via the entry for
the inotify file descriptor in the process's
-.IR /proc/[pid]/fdinfo
+.I /proc/[pid]/fdinfo
directory.
See
.BR proc (5)
@@ -667,7 +667,7 @@ Furthermore, various pseudo-filesystems such as
.IR /proc ,
.IR /sys ,
and
-.IR /dev/pts
+.I /dev/pts
are not monitorable with inotify.
.PP
The inotify API does not report file accesses and modifications that
@@ -755,7 +755,7 @@ event pair generated by
is thus inherently racy.
(Don't forget that if an object is renamed outside of a monitored directory,
there may not even be an
-.BR IN_MOVED_TO
+.B IN_MOVED_TO
event.)
Heuristic approaches (e.g., assume the events are always consecutive)
can be used to ensure a match in most cases,
@@ -860,7 +860,7 @@ The following program demonstrates the usage of the inotify API.
It marks the directories passed as a command-line arguments
and waits for events of type
.BR IN_OPEN ,
-.BR IN_CLOSE_NOWRITE
+.B IN_CLOSE_NOWRITE
and
.BR IN_CLOSE_WRITE .
.PP
@@ -1096,5 +1096,5 @@ main(int argc, char* argv[])
.BR stat (2),
.BR fanotify (7)
.PP
-.IR Documentation/filesystems/inotify.txt
+.I Documentation/filesystems/inotify.txt
in the Linux kernel source tree
diff --git a/man7/ip.7 b/man7/ip.7
index 02dd47f2a..9690f5359 100644
--- a/man7/ip.7
+++ b/man7/ip.7
@@ -168,7 +168,7 @@ when this setting is missing.
.I sin_port
contains the port in network byte order.
The port numbers below 1024 are called
-.IR "privileged ports"
+.I privileged ports
(or sometimes:
.IR "reserved ports" ).
Only a privileged process
@@ -192,7 +192,7 @@ member of
contains the host interface address in network byte order.
.I in_addr
should be assigned one of the
-.BR INADDR_*
+.B INADDR_*
values
(e.g.,
.BR INADDR_LOOPBACK )
@@ -367,7 +367,7 @@ in a way that allows sharing a source port as long as the 4-tuple is unique.
Stop receiving multicast data from a specific source in a given group.
This is valid only after the application has subscribed
to the multicast group using either
-.BR IP_ADD_MEMBERSHIP
+.B IP_ADD_MEMBERSHIP
or
.BR IP_ADD_SOURCE_MEMBERSHIP .
.IP
@@ -407,7 +407,7 @@ without requiring the underlying network interface or the
specified dynamic IP address to be up at the time that
the application is trying to bind to it.
This option is the per-socket equivalent of the
-.IR ip_nonlocal_bind
+.I ip_nonlocal_bind
.I /proc
interface described below.
.TP
@@ -450,7 +450,7 @@ struct ip_msfilter {
.in
.PP
There are two macros,
-.BR MCAST_INCLUDE
+.B MCAST_INCLUDE
and
.BR MCAST_EXCLUDE ,
which can be used to specify the filtering mode.
@@ -553,7 +553,7 @@ It is possible to implement RFC 4821 MTU probing with
or
.B SOCK_RAW
sockets by setting a value of
-.BR IP_PMTUDISC_PROBE
+.B IP_PMTUDISC_PROBE
(available since Linux 2.6.22).
This is also particularly useful for diagnostic tools such as
.BR tracepath (8)
@@ -944,7 +944,7 @@ packets going to the foreign address are routed through the TProxy box
socket option).
Enabling this socket option requires superuser privileges
(the
-.BR CAP_NET_ADMIN
+.B CAP_NET_ADMIN
capability).
.IP
TProxy redirection with the iptables TPROXY target also requires that
@@ -957,7 +957,7 @@ sent from this socket.
.BR IP_UNBLOCK_SOURCE " (since Linux 2.4.22 / 2.5.68)"
Unblock previously blocked multicast source.
Returns
-.BR EADDRNOTAVAIL
+.B EADDRNOTAVAIL
when given source is not being blocked.
.IP
Argument is an
@@ -1054,13 +1054,13 @@ is called on a datagram socket that was not previously bound.
.RE
.IP
Allocation of ephemeral ports starts with the first number in
-.IR ip_local_port_range
+.I ip_local_port_range
and ends with the second number.
If the range of ephemeral ports is exhausted,
then the relevant system call returns an error (but see BUGS).
.IP
Note that the port range in
-.IR ip_local_port_range
+.I ip_local_port_range
should not conflict with the ports used by masquerading
(although the case is handled).
Also, arbitrary choices may cause problems with some firewall packet
@@ -1231,7 +1231,7 @@ and
.BR IP_RECVERR ,
.BR IP_ROUTER_ALERT ,
and
-.BR IP_TRANSPARENT
+.B IP_TRANSPARENT
are Linux-specific.
.\" IP_PASSSEC is Linux-specific
.\" IP_XFRM_POLICY is Linux-specific
--
2.20.1
