Use a single-font-style macro (".B", ".I") for a single argument.
The output from "nroff" and "groff" is unchanged.
Signed-off-by: Bjarni Ingi Gislason <bjarniig@xxxxxxxxx>
---
man2/timer_create.2 | 26 +++++++++++++-------------
man2/timer_settime.2 | 6 +++---
man2/timerfd_create.2 | 26 +++++++++++++-------------
man2/truncate.2 | 2 +-
4 files changed, 30 insertions(+), 30 deletions(-)
diff --git a/man2/timer_create.2 b/man2/timer_create.2
index cbcc2b140..b493a1d5b 100644
--- a/man2/timer_create.2
+++ b/man2/timer_create.2
@@ -84,12 +84,12 @@ Like
.BR CLOCK_MONOTONIC ,
this is a monotonically increasing clock.
However, whereas the
-.BR CLOCK_MONOTONIC
+.B CLOCK_MONOTONIC
clock does not measure the time while a system is suspended, the
-.BR CLOCK_BOOTTIME
+.B CLOCK_BOOTTIME
clock does include the time during which the system is suspended.
This is useful for applications that need to be suspend-aware.
-.BR CLOCK_REALTIME
+.B CLOCK_REALTIME
is not suitable for such applications, since that clock is affected
by discontinuous changes to the system clock.
.TP
@@ -133,12 +133,12 @@ The
.I sevp.sigev_notify
field can have the following values:
.TP
-.BR SIGEV_NONE
+.B SIGEV_NONE
Don't asynchronously notify when the timer expires.
Progress of the timer can be monitored using
.BR timer_gettime (2).
.TP
-.BR SIGEV_SIGNAL
+.B SIGEV_SIGNAL
Upon timer expiration, generate the signal
.I sigev_signo
for the process.
@@ -156,7 +156,7 @@ at most one signal is queued to the process for a given timer; see
.BR timer_getoverrun (2)
for more details.
.TP
-.BR SIGEV_THREAD
+.B SIGEV_THREAD
Upon timer expiration, invoke
.I sigev_notify_function
as if it were the start function of a new thread.
@@ -171,7 +171,7 @@ but the signal is targeted at the thread whose ID is given in
.IR sigev_notify_thread_id ,
which must be a thread in the same process as the caller.
The
-.IR sigev_notify_thread_id
+.I sigev_notify_thread_id
field specifies a kernel thread ID, that is, the value returned by
.BR clone (2)
or
@@ -210,7 +210,7 @@ Clock ID,
.IR sigev_notify ,
.IR sigev_signo ,
or
-.IR sigev_notify_thread_id
+.I sigev_notify_thread_id
is invalid.
.TP
.B ENOMEM
@@ -233,7 +233,7 @@ The kernel preallocates a "queued real-time signal"
for each timer created using
.BR timer_create ().
Consequently, the number of timers is limited by the
-.BR RLIMIT_SIGPENDING
+.B RLIMIT_SIGPENDING
resource limit (see
.BR setrlimit (2)).
.PP
@@ -259,7 +259,7 @@ Return the overrun count for the last timer expiration.
Disarm and delete a timer.
.PP
Since Linux 3.10, the
-.IR /proc/[pid]/timers
+.I /proc/[pid]/timers
file can be used to list the POSIX timers for the process with PID
.IR pid .
See
@@ -270,7 +270,7 @@ Since Linux 4.10,
.\" baa73d9e478ff32d62f3f9422822b59dd9a95a21
support for POSIX timers is a configurable option that is enabled by default.
Kernel support can be disabled via the
-.BR CONFIG_POSIX_TIMERS
+.B CONFIG_POSIX_TIMERS
option.
.\"
.SS C library/kernel differences
@@ -279,7 +279,7 @@ Part of the implementation of the POSIX timers API is provided by glibc.
In particular:
.IP * 3
Much of the functionality for
-.BR SIGEV_THREAD
+.B SIGEV_THREAD
is implemented within glibc, rather than the kernel.
(This is necessarily so,
since the thread involved in handling the notification is one
@@ -288,7 +288,7 @@ Although the notification delivered to the process is via a thread,
internally the NPTL implementation uses a
.I sigev_notify
value of
-.BR SIGEV_THREAD_ID
+.B SIGEV_THREAD_ID
along with a real-time signal that is reserved by the implementation (see
.BR nptl (7)).
.IP *
diff --git a/man2/timer_settime.2 b/man2/timer_settime.2
index e2b5d8c32..24c5ef16f 100644
--- a/man2/timer_settime.2
+++ b/man2/timer_settime.2
@@ -160,15 +160,15 @@ in the buffer pointed to by
The time remaining until the next timer expiration is returned in
.IR curr_value->it_value ;
this is always a relative value, regardless of whether the
-.BR TIMER_ABSTIME
+.B TIMER_ABSTIME
flag was used when arming the timer.
If the value returned in
-.IR curr_value->it_value
+.I curr_value->it_value
is zero, then the timer is currently disarmed.
The timer interval is returned in
.IR curr_value->it_interval .
If the value returned in
-.IR curr_value->it_interval
+.I curr_value->it_interval
is zero, then this is a "one-shot" timer.
.SH RETURN VALUE
On success,
diff --git a/man2/timerfd_create.2 b/man2/timerfd_create.2
index b4e3672fb..7de285189 100644
--- a/man2/timerfd_create.2
+++ b/man2/timerfd_create.2
@@ -82,12 +82,12 @@ Like
.BR CLOCK_MONOTONIC ,
this is a monotonically increasing clock.
However, whereas the
-.BR CLOCK_MONOTONIC
+.B CLOCK_MONOTONIC
clock does not measure the time while a system is suspended, the
-.BR CLOCK_BOOTTIME
+.B CLOCK_BOOTTIME
clock does include the time during which the system is suspended.
This is useful for applications that need to be suspend-aware.
-.BR CLOCK_REALTIME
+.B CLOCK_REALTIME
is not suitable for such applications, since that clock is affected
by discontinuous changes to the system clock.
.TP
@@ -113,13 +113,13 @@ The current value of each of these clocks can be retrieved using
.BR clock_gettime (2).
.PP
Starting with Linux 2.6.27, the following values may be bitwise ORed in
-.IR flags
+.I flags
to change the behavior of
.BR timerfd_create ():
.TP 14
.B TFD_NONBLOCK
Set the
-.BR O_NONBLOCK
+.B O_NONBLOCK
file status flag on the open file description (see
.BR open (2))
referred to by the new file descriptor.
@@ -212,11 +212,11 @@ The timer will expire when the value of the timer's
clock reaches the value specified in
.IR new_value.it_value .
.TP
-.BR TFD_TIMER_CANCEL_ON_SET
+.B TFD_TIMER_CANCEL_ON_SET
If this flag is specified along with
.B TFD_TIMER_ABSTIME
and the clock for this timer is
-.BR CLOCK_REALTIME
+.B CLOCK_REALTIME
or
.BR CLOCK_REALTIME_ALARM ,
then mark this timer as cancelable if the real-time clock
@@ -244,7 +244,7 @@ following.
returns, in
.IR curr_value ,
an
-.IR itimerspec
+.I itimerspec
structure that contains the current setting of the timer
referred to by the file descriptor
.IR fd .
@@ -256,7 +256,7 @@ until the timer will next expire.
If both fields of this structure are zero,
then the timer is currently disarmed.
This field always contains a relative value, regardless of whether the
-.BR TFD_TIMER_ABSTIME
+.B TFD_TIMER_ABSTIME
flag was specified when setting the timer.
.PP
The
@@ -304,19 +304,19 @@ fails with the error
if the size of the supplied buffer is less than 8 bytes.
.IP
If the associated clock is either
-.BR CLOCK_REALTIME
+.B CLOCK_REALTIME
or
.BR CLOCK_REALTIME_ALARM ,
the timer is absolute
.RB ( TFD_TIMER_ABSTIME ),
and the flag
-.BR TFD_TIMER_CANCEL_ON_SET
+.B TFD_TIMER_CANCEL_ON_SET
was specified when calling
.BR timerfd_settime (),
then
.BR read (2)
fails with the error
-.BR ECANCELED
+.B ECANCELED
if the real-time clock undergoes a discontinuous change.
(This allows the reading application to discover
such discontinuous changes to the clock.)
@@ -353,7 +353,7 @@ Once the number is set, any waiter on the timer is woken up.
The only purpose of this command is to restore the expirations
for the purpose of checkpoint/restore.
This operation is available only if the kernel was configured with the
-.BR CONFIG_CHECKPOINT_RESTORE
+.B CONFIG_CHECKPOINT_RESTORE
option.
.RE
.TP
diff --git a/man2/truncate.2 b/man2/truncate.2
index 0e6a7ab19..9ae7a7299 100644
--- a/man2/truncate.2
+++ b/man2/truncate.2
@@ -266,7 +266,7 @@ for the reasons described in
.SH BUGS
A header file bug in glibc 2.12 meant that the minimum value of
.\" http://sourceware.org/bugzilla/show_bug.cgi?id=12037
-.BR _POSIX_C_SOURCE
+.B _POSIX_C_SOURCE
required to expose the declaration of
.BR ftruncate ()
was 200809L instead of 200112L.
--
2.20.1
