Many pages: Use \[bu] instead of \(bu

Signed-off-by: Alejandro Colomar <alx@kernel.org>
author: Alejandro Colomar <alx@kernel.org> 2023-02-05 23:14:38 +0100
committer: Alejandro Colomar <alx@kernel.org> 2023-02-05 23:14:42 +0100
commit: cdede5cdd1b0ba75135d3b32d96354026e96f866 (patch)
tree: f21d7604d25b2de607ef5471e5e180094231e046 /man7/signal.7
parent: f29fc8dcf0da15a596a7cdc7e5a0b2932100b522 (diff)
download: man-pages-cdede5cdd1b0ba75135d3b32d96354026e96f866.tar.gz
1 files changed, 41 insertions, 41 deletions
diff --git a/man7/signal.7 b/man7/signal.7
index 73accfd2da..ea279d0e2a 100644
--- a/man7/signal.7
+++ b/man7/signal.7
@@ -136,7 +136,7 @@ to block execution until the signal is delivered,
 at which point the kernel returns information about the
 signal to the caller.
 There are two general ways to do this:
-.IP \(bu 3
+.IP \[bu] 3
 .BR sigwaitinfo (2),
 .BR sigtimedwait (2),
 and
@@ -144,7 +144,7 @@ and
 suspend execution until one of the signals in a specified
 set is delivered.
 Each of these calls returns information about the delivered signal.
-.IP \(bu
+.IP \[bu]
 .BR signalfd (2)
 returns a file descriptor that can be used to read information
 about signals that are delivered to the caller.
@@ -264,16 +264,16 @@ Various pieces of signal-related context are saved
 into a special frame that is created on the stack.
 The saved information includes:
 .RS
-.IP \(bu 3
+.IP \[bu] 3
 the program counter register
 (i.e., the address of the next instruction in the main program that
 should be executed when the signal handler returns);
-.IP \(bu
+.IP \[bu]
 architecture-specific register state required for resuming the
 interrupted program;
-.IP \(bu
+.IP \[bu]
 the thread's current signal mask;
-.IP \(bu
+.IP \[bu]
 the thread's alternate signal stack settings.
 .RE
 .IP
@@ -512,7 +512,7 @@ SIGUNUSED	31	\-	\-	31
 .TE
 .PP
 Note the following:
-.IP \(bu 3
+.IP \[bu] 3
 Where defined,
 .B SIGUNUSED
 is synonymous with
@@ -520,7 +520,7 @@ is synonymous with
 Since glibc 2.26,
 .B SIGUNUSED
 is no longer defined on any architecture.
-.IP \(bu
+.IP \[bu]
 Signal 29 is
 .BR SIGINFO / SIGPWR
 (synonyms for the same value) on Alpha but
@@ -569,11 +569,11 @@ The default action for an unhandled real-time signal is to terminate the
 receiving process.
 .PP
 Real-time signals are distinguished by the following:
-.IP \(bu 3
+.IP \[bu] 3
 Multiple instances of real-time signals can be queued.
 By contrast, if multiple instances of a standard signal are delivered
 while that signal is currently blocked, then only one instance is queued.
-.IP \(bu
+.IP \[bu]
 If the signal is sent using
 .BR sigqueue (3),
 an accompanying value (either an integer or a pointer) can be sent
@@ -593,7 +593,7 @@ and
 .I si_uid
 fields of this structure can be used to obtain the PID
 and real user ID of the process sending the signal.
-.IP \(bu
+.IP \[bu]
 Real-time signals are delivered in a guaranteed order.
 Multiple real-time signals of the same type are delivered in the order
 they were sent.
@@ -653,9 +653,9 @@ Linux 2.0 and earlier	Linux 2.2 and later
 .SS Interruption of system calls and library functions by signal handlers
 If a signal handler is invoked while a system call or library
 function call is blocked, then either:
-.IP \(bu 3
+.IP \[bu] 3
 the call is automatically restarted after the signal handler returns; or
-.IP \(bu
+.IP \[bu]
 the call fails with the error
 .BR EINTR .
 .PP
@@ -675,7 +675,7 @@ flag was used; otherwise the call fails with the error
 .BR EINTR :
 .\" The following system calls use ERESTARTSYS,
 .\" so that they are restartable
-.IP \(bu 3
+.IP \[bu] 3
 .BR read (2),
 .BR readv (2),
 .BR write (2),
@@ -691,18 +691,18 @@ then the call will return a success status
 (normally, the number of bytes transferred).
 Note that a (local) disk is not a slow device according to this definition;
 I/O operations on disk devices are not interrupted by signals.
-.IP \(bu
+.IP \[bu]
 .BR open (2),
 if it can block (e.g., when opening a FIFO; see
 .BR fifo (7)).
-.IP \(bu
+.IP \[bu]
 .BR wait (2),
 .BR wait3 (2),
 .BR wait4 (2),
 .BR waitid (2),
 and
 .BR waitpid (2).
-.IP \(bu
+.IP \[bu]
 Socket interfaces:
 .\" If a timeout (setsockopt()) is in effect on the socket, then these
 .\" system calls switch to using EINTR.  Consequently, they and are not
@@ -720,7 +720,7 @@ and
 .BR sendmsg (2),
 .\" FIXME What about sendmmsg()?
 unless a timeout has been set on the socket (see below).
-.IP \(bu
+.IP \[bu]
 File locking interfaces:
 .BR flock (2)
 and
@@ -730,30 +730,30 @@ and
 .B F_OFD_SETLKW
 operations of
 .BR fcntl (2)
-.IP \(bu
+.IP \[bu]
 POSIX message queue interfaces:
 .BR mq_receive (3),
 .BR mq_timedreceive (3),
 .BR mq_send (3),
 and
 .BR mq_timedsend (3).
-.IP \(bu
+.IP \[bu]
 .BR futex (2)
 .B FUTEX_WAIT
 (since Linux 2.6.22;
 .\" commit 72c1bbf308c75a136803d2d76d0e18258be14c7a
 beforehand, always failed with
 .BR EINTR ).
-.IP \(bu
+.IP \[bu]
 .BR getrandom (2).
-.IP \(bu
+.IP \[bu]
 .BR pthread_mutex_lock (3),
 .BR pthread_cond_wait (3),
 and related APIs.
-.IP \(bu
+.IP \[bu]
 .BR futex (2)
 .BR FUTEX_WAIT_BITSET .
-.IP \(bu
+.IP \[bu]
 POSIX semaphore interfaces:
 .BR sem_wait (3)
 and
@@ -762,7 +762,7 @@ and
 .\" as a consequence of the 2.6.22 changes in the futex() implementation
 beforehand, always failed with
 .BR EINTR ).
-.IP \(bu
+.IP \[bu]
 .BR read (2)
 from an
 .BR inotify (7)
@@ -781,7 +781,7 @@ they always fail with the error
 when interrupted by a signal handler:
 .\" These are the system calls that give EINTR or ERESTARTNOHAND
 .\" on interruption by a signal handler.
-.IP \(bu 3
+.IP \[bu] 3
 "Input" socket interfaces, when a timeout
 .RB ( SO_RCVTIMEO )
 has been set on the socket using
@@ -795,7 +795,7 @@ has been set on the socket using
 argument),
 and
 .BR recvmsg (2).
-.IP \(bu
+.IP \[bu]
 "Output" socket interfaces, when a timeout
 .RB ( SO_RCVTIMEO )
 has been set on the socket using
@@ -806,14 +806,14 @@ has been set on the socket using
 and
 .BR sendmsg (2).
 .\" FIXME What about sendmmsg()?
-.IP \(bu
+.IP \[bu]
 Interfaces used to wait for signals:
 .BR pause (2),
 .BR sigsuspend (2),
 .BR sigtimedwait (2),
 and
 .BR sigwaitinfo (2).
-.IP \(bu
+.IP \[bu]
 File descriptor multiplexing interfaces:
 .BR epoll_wait (2),
 .BR epoll_pwait (2),
@@ -822,7 +822,7 @@ File descriptor multiplexing interfaces:
 .BR select (2),
 and
 .BR pselect (2).
-.IP \(bu
+.IP \[bu]
 System V IPC interfaces:
 .\" On some other systems, SA_RESTART does restart these system calls
 .BR msgrcv (2),
@@ -830,13 +830,13 @@ System V IPC interfaces:
 .BR semop (2),
 and
 .BR semtimedop (2).
-.IP \(bu
+.IP \[bu]
 Sleep interfaces:
 .BR clock_nanosleep (2),
 .BR nanosleep (2),
 and
 .BR usleep (3).
-.IP \(bu
+.IP \[bu]
 .BR io_getevents (2).
 .PP
 The
@@ -863,7 +863,7 @@ This behavior is not sanctioned by POSIX.1, and doesn't occur
 on other systems.
 .PP
 The Linux interfaces that display this behavior are:
-.IP \(bu 3
+.IP \[bu] 3
 "Input" socket interfaces, when a timeout
 .RB ( SO_RCVTIMEO )
 has been set on the socket using
@@ -877,7 +877,7 @@ has been set on the socket using
 argument),
 and
 .BR recvmsg (2).
-.IP \(bu
+.IP \[bu]
 "Output" socket interfaces, when a timeout
 .RB ( SO_RCVTIMEO )
 has been set on the socket using
@@ -891,33 +891,33 @@ and
 if a send timeout
 .RB ( SO_SNDTIMEO )
 has been set.
-.IP \(bu
+.IP \[bu]
 .BR epoll_wait (2),
 .BR epoll_pwait (2).
-.IP \(bu
+.IP \[bu]
 .BR semop (2),
 .BR semtimedop (2).
-.IP \(bu
+.IP \[bu]
 .BR sigtimedwait (2),
 .BR sigwaitinfo (2).
-.IP \(bu
+.IP \[bu]
 Linux 3.7 and earlier:
 .BR read (2)
 from an
 .BR inotify (7)
 file descriptor
 .\" commit 1ca39ab9d21ac93f94b9e3eb364ea9a5cf2aba06
-.IP \(bu
+.IP \[bu]
 Linux 2.6.21 and earlier:
 .BR futex (2)
 .BR FUTEX_WAIT ,
 .BR sem_timedwait (3),
 .BR sem_wait (3).
-.IP \(bu
+.IP \[bu]
 Linux 2.6.8 and earlier:
 .BR msgrcv (2),
 .BR msgsnd (2).
-.IP \(bu
+.IP \[bu]
 Linux 2.4 and earlier:
 .BR nanosleep (2).
 .SH STANDARDS
author	Alejandro Colomar <alx@kernel.org>	2023-02-05 23:14:38 +0100
committer	Alejandro Colomar <alx@kernel.org>	2023-02-05 23:14:42 +0100
commit	cdede5cdd1b0ba75135d3b32d96354026e96f866 (patch)
tree	f21d7604d25b2de607ef5471e5e180094231e046 /man7/signal.7
parent	f29fc8dcf0da15a596a7cdc7e5a0b2932100b522 (diff)
download	man-pages-cdede5cdd1b0ba75135d3b32d96354026e96f866.tar.gz