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 /man5
parent: f29fc8dcf0da15a596a7cdc7e5a0b2932100b522 (diff)
download: man-pages-cdede5cdd1b0ba75135d3b32d96354026e96f866.tar.gz
8 files changed, 76 insertions, 76 deletions
diff --git a/man5/core.5 b/man5/core.5
index 4b8c8290b9..816712149f 100644
--- a/man5/core.5
+++ b/man5/core.5
@@ -26,7 +26,7 @@ for details.
 .PP
 There are various circumstances in which a core dump file is
 not produced:
-.IP \(bu 3
+.IP \[bu] 3
 The process does not have permission to write the core file.
 (By default, the core file is called
 .I core
@@ -43,18 +43,18 @@ or if a file with the same name exists and
 is not writable
 or is not a regular file
 (e.g., it is a directory or a symbolic link).
-.IP \(bu
+.IP \[bu]
 A (writable, regular) file with the same name as would be used for the
 core dump already exists, but there is more than one hard link to that
 file.
-.IP \(bu
+.IP \[bu]
 The filesystem where the core dump file would be created is full;
 or has run out of inodes; or is mounted read-only;
 or the user has reached their quota for the filesystem.
-.IP \(bu
+.IP \[bu]
 The directory in which the core dump file is to be created does
 not exist.
-.IP \(bu
+.IP \[bu]
 The
 .B RLIMIT_CORE
 (core file size) or
@@ -70,14 +70,14 @@ in
 However,
 .B RLIMIT_CORE
 will be ignored if the system is configured to pipe core dumps to a program.
-.IP \(bu
+.IP \[bu]
 The binary being executed by the process does not have read
 permission enabled.
 (This is a security measure to
 ensure that an executable whose contents are not readable
 does not produce a\[em]possibly readable\[em]core dump containing
 an image of the executable.)
-.IP \(bu
+.IP \[bu]
 The process is executing a set-user-ID (set-group-ID) program
 that is owned by a user (group) other than the real user (group)
 ID of the process,
@@ -92,7 +92,7 @@ operation, and the description of the
 .\" and PR_SET_DUMPABLE to this page?
 file in
 .BR proc (5).)
-.IP \(bu
+.IP \[bu]
 .I /proc/sys/kernel/core_pattern
 is empty and
 .I /proc/sys/kernel/core_uses_pid
@@ -109,7 +109,7 @@ and such files are hidden unless one uses the
 .BR ls (1)
 .I \-a
 option.
-.IP \(bu
+.IP \[bu]
 (Since Linux 3.7)
 .\" commit 046d662f481830e652ac34cd112249adde16452a
 The kernel was configured without the
@@ -287,33 +287,33 @@ the executable name.
 Instead of being written to a file, the core dump is given as
 standard input to the program.
 Note the following points:
-.IP \(bu 3
+.IP \[bu] 3
 The program must be specified using an absolute pathname (or a
 pathname relative to the root directory, \fI/\fP),
 and must immediately follow the '|' character.
-.IP \(bu
+.IP \[bu]
 The command-line arguments can include any of
 the % specifiers listed above.
 For example, to pass the PID of the process that is being dumped, specify
 .I %p
 in an argument.
-.IP \(bu
+.IP \[bu]
 The process created to run the program runs as user and group
 .IR root .
-.IP \(bu
+.IP \[bu]
 Running as
 .I root
 does not confer any exceptional security bypasses.
 Namely, LSMs (e.g., SELinux) are still active and may prevent the handler
 from accessing details about the crashed process via
 .IR /proc/ pid.
-.IP \(bu
+.IP \[bu]
 The program pathname is interpreted with respect to the initial mount namespace
 as it is always executed there.
 It is not affected by the settings
 (e.g., root directory, mount namespace, current working directory)
 of the crashing process.
-.IP \(bu
+.IP \[bu]
 The process runs in the initial namespaces
 (PID, mount, user, and so on)
 and not in the namespaces of the crashing process.
@@ -322,7 +322,7 @@ One can utilize specifiers such as
 to find the right
 .IR /proc/ pid
 directory and probe/enter the crashing process's namespaces if needed.
-.IP \(bu
+.IP \[bu]
 The process starts with its current working directory
 as the root directory.
 If desired, it is possible change to the working directory of
@@ -330,11 +330,11 @@ the dumping process by employing the value provided by the
 .I %P
 specifier to change to the location of the dumping process via
 .IR /proc/ pid /cwd .
-.IP \(bu
+.IP \[bu]
 Command-line arguments can be supplied to the
 program (since Linux 2.6.24),
 delimited by white space (up to a total line length of 128 bytes).
-.IP \(bu
+.IP \[bu]
 The
 .B RLIMIT_CORE
 limit is not enforced for core dumps that are piped to a program
diff --git a/man5/locale.5 b/man5/locale.5
index 77771438e4..b0a21560fb 100644
--- a/man5/locale.5
+++ b/man5/locale.5
@@ -58,32 +58,32 @@ provided locale definition file should be used as a reference to follow
 common glibc conventions.
 .SS Locale category sections
 The following category sections are defined by POSIX:
-.IP \(bu 3
+.IP \[bu] 3
 .B LC_CTYPE
-.IP \(bu
+.IP \[bu]
 .B LC_COLLATE
-.IP \(bu
+.IP \[bu]
 .B LC_MESSAGES
-.IP \(bu
+.IP \[bu]
 .B LC_MONETARY
-.IP \(bu
+.IP \[bu]
 .B LC_NUMERIC
-.IP \(bu
+.IP \[bu]
 .B LC_TIME
 .PP
 In addition, since glibc 2.2,
 the GNU C library supports the following nonstandard categories:
-.IP \(bu 3
+.IP \[bu] 3
 .B LC_ADDRESS
-.IP \(bu
+.IP \[bu]
 .B LC_IDENTIFICATION
-.IP \(bu
+.IP \[bu]
 .B LC_MEASUREMENT
-.IP \(bu
+.IP \[bu]
 .B LC_NAME
-.IP \(bu
+.IP \[bu]
 .B LC_PAPER
-.IP \(bu
+.IP \[bu]
 .B LC_TELEPHONE
 .PP
 See
@@ -1262,7 +1262,7 @@ and
 states at
 https://sourceware.org/glibc/wiki/Locales
 the following:
-.IP \(bu 3
+.IP \[bu] 3
 The value of the second
 .I week
 list item specifies the base of the
@@ -1270,14 +1270,14 @@ list item specifies the base of the
 and
 .I day
 lists.
-.IP \(bu
+.IP \[bu]
 .I first_weekday
 specifies the offset of the first day-of-week in the
 .I abday
 and
 .I day
 lists.
-.IP \(bu
+.IP \[bu]
 For compatibility reasons, all glibc locales should set the value of the
 second
 .I week
diff --git a/man5/nscd.conf.5 b/man5/nscd.conf.5
index fa330d2966..154a99b6c1 100644
--- a/man5/nscd.conf.5
+++ b/man5/nscd.conf.5
@@ -299,25 +299,25 @@ the value of the
 attribute.
 .PP
 Please consider the following advice carefully:
-.IP \(bu 3
+.IP \[bu] 3
 If your application will make a second request for the same name,
 after more than 1 TTL but before
 .B reload\-count
 TTLs,
 and is sensitive to the latency of a cache miss,
 then reloading may be a good idea for you.
-.IP \(bu
+.IP \[bu]
 If your name service is configured to return very short TTLs,
 and your applications only make requests rarely under normal circumstances,
 then reloading may result in additional load on your backing name service
 without any benefit to applications,
 which is probably a bad idea for you.
-.IP \(bu
+.IP \[bu]
 If your name service capacity is limited,
 reloading may have the surprising effect of
 increasing load on your name service instead of reducing it,
 and may be a bad idea for you.
-.IP \(bu
+.IP \[bu]
 Setting
 .B reload\-count
 to
diff --git a/man5/nsswitch.conf.5 b/man5/nsswitch.conf.5
index 4d0cbc9dc6..53b590fd24 100644
--- a/man5/nsswitch.conf.5
+++ b/man5/nsswitch.conf.5
@@ -122,11 +122,11 @@ services:       nis [NOTFOUND=return] files
 .PP
 The first column is the database name.
 The remaining columns specify:
-.IP \(bu 3
+.IP \[bu] 3
 One or more service specifications, for example, "files", "db", or "nis".
 The order of the services on the line determines the order in which
 those services will be queried, in turn, until a result is found.
-.IP \(bu
+.IP \[bu]
 Optional actions to perform if a particular result is obtained
 from the preceding service, for example, "[NOTFOUND=return]".
 .PP
diff --git a/man5/proc.5 b/man5/proc.5
index 6efdc51cbf..7d09da6bb0 100644
--- a/man5/proc.5
+++ b/man5/proc.5
@@ -245,12 +245,12 @@ things work as expected for the container "root" user.
 .IP
 The process's "dumpable" attribute may change for the following reasons:
 .RS
-.IP \(bu 3
+.IP \[bu] 3
 The attribute was explicitly set via the
 .BR prctl (2)
 .B PR_SET_DUMPABLE
 operation.
-.IP \(bu
+.IP \[bu]
 The attribute was reset to the value in the file
 .I /proc/sys/fs/suid_dumpable
 (described below), for the reasons described in
@@ -1653,7 +1653,7 @@ with increases (+) or decreases (\-) for factors including:
 .\" See mm/oom_kill.c::oom_badness() after Linux 2.6.36
 .\" commit a63d83f427fbce97a6cea0db2e64b0eb8435cd10
 .RS
-.IP \(bu 3
+.IP \[bu] 3
 whether the process is privileged (\-).
 .\" More precisely, if it has CAP_SYS_ADMIN or (pre 2.6.36) CAP_SYS_RESOURCE
 .RE
@@ -1661,16 +1661,16 @@ whether the process is privileged (\-).
 Before Linux 2.6.36
 the following factors were also used in the calculation of oom_score:
 .RS
-.IP \(bu 3
+.IP \[bu] 3
 whether the process creates a lot of children using
 .BR fork (2)
 (+);
-.IP \(bu
+.IP \[bu]
 whether the process has been running a long time,
 or has used a lot of CPU time (\-);
-.IP \(bu
+.IP \[bu]
 whether the process has a low nice value (i.e., > 0) (+); and
-.IP \(bu
+.IP \[bu]
 whether the process is making direct hardware access (\-).
 .\" More precisely, if it has CAP_SYS_RAWIO
 .RE
@@ -4316,16 +4316,16 @@ pseudo-file.
 This value is not reliable, for the following reasons:
 .\" See kernel commit 9c240d757658a3ae9968dd309e674c61f07c7f48
 .RS
-.IP \(bu 3
+.IP \[bu] 3
 The CPU will not wait for I/O to complete;
 iowait is the time that a task is waiting for I/O to complete.
 When a CPU goes into idle state for outstanding task I/O,
 another task will be scheduled on this CPU.
-.IP \(bu
+.IP \[bu]
 On a multi-core CPU,
 the task waiting for I/O to complete is not running on any CPU,
 so the iowait of each CPU is difficult to calculate.
-.IP \(bu
+.IP \[bu]
 The value in this field may
 .I decrease
 in certain conditions.
@@ -4484,19 +4484,19 @@ The file contains six numbers,
 .I want_pages
 (pages requested by system) and two dummy values.
 .RS
-.IP \(bu 3
+.IP \[bu] 3
 .I nr_dentry
 is the number of allocated dentries (dcache entries).
 This field is unused in Linux 2.2.
-.IP \(bu
+.IP \[bu]
 .I nr_unused
 is the number of unused dentries.
-.IP \(bu
+.IP \[bu]
 .I age_limit
 .\" looks like this is unused in Linux 2.2 to Linux 2.6
 is the age in seconds after which dcache entries
 can be reclaimed when memory is short.
-.IP \(bu
+.IP \[bu]
 .I want_pages
 .\" looks like this is unused in Linux 2.2 to Linux 2.6
 is nonzero when the kernel has called shrink_dcache_pages() and the
@@ -4725,28 +4725,28 @@ When the value in this file is 1,
 a hard link can be created to a target file
 only if one of the following conditions is true:
 .RS
-.IP \(bu 3
+.IP \[bu] 3
 The calling process has the
 .B CAP_FOWNER
 capability in its user namespace
 and the file UID has a mapping in the namespace.
-.IP \(bu
+.IP \[bu]
 The filesystem UID of the process creating the link matches
 the owner (UID) of the target file
 (as described in
 .BR credentials (7),
 a process's filesystem UID is normally the same as its effective UID).
-.IP \(bu
+.IP \[bu]
 All of the following conditions are true:
 .RS 4
-.IP \(bu 3
+.IP \[bu] 3
 the target is a regular file;
-.IP \(bu
+.IP \[bu]
 the target file does not have its set-user-ID mode bit enabled;
-.IP \(bu
+.IP \[bu]
 the target file does not have both its set-group-ID and
 group-executable mode bits enabled; and
-.IP \(bu
+.IP \[bu]
 the caller has permission to read and write the target file
 (either via the file's permissions mask or because it has
 suitable capabilities).
@@ -4801,15 +4801,15 @@ no restrictions are placed on following symbolic links
 When the value in this file is 1, symbolic links are followed only
 in the following circumstances:
 .RS
-.IP \(bu 3
+.IP \[bu] 3
 the filesystem UID of the process following the link matches
 the owner (UID) of the symbolic link
 (as described in
 .BR credentials (7),
 a process's filesystem UID is normally the same as its effective UID);
-.IP \(bu
+.IP \[bu]
 the link is not in a sticky world-writable directory; or
-.IP \(bu
+.IP \[bu]
 the symbolic link and its parent directory have the same owner (UID)
 .RE
 .IP
@@ -5890,18 +5890,18 @@ CommitLimit = (total_RAM \- total_huge_TLB) *
 .IP
 where:
 .RS
-.IP \(bu 3
+.IP \[bu] 3
 .I total_RAM
 is the total amount of RAM on the system;
-.IP \(bu
+.IP \[bu]
 .I total_huge_TLB
 is the amount of memory set aside for huge pages;
-.IP \(bu
+.IP \[bu]
 .I overcommit_ratio
 is the value in
 .IR /proc/sys/vm/overcommit_ratio ;
 and
-.IP \(bu
+.IP \[bu]
 .I total_swap
 is the amount of swap space.
 .RE
diff --git a/man5/rpc.5 b/man5/rpc.5
index 29bc354a60..cecc2f6078 100644
--- a/man5/rpc.5
+++ b/man5/rpc.5
@@ -20,11 +20,11 @@ can be used in place of RPC program numbers.
 Each line has the following information:
 .PP
 .PD 0
-.IP \(bu 3
+.IP \[bu] 3
 name of server for the RPC program
-.IP \(bu
+.IP \[bu]
 RPC program number
-.IP \(bu
+.IP \[bu]
 aliases
 .PD
 .PP
diff --git a/man5/slabinfo.5 b/man5/slabinfo.5
index 6f286d3d9c..5ee659f8ea 100644
--- a/man5/slabinfo.5
+++ b/man5/slabinfo.5
@@ -39,11 +39,11 @@ The next line lists the names of the columns in the remaining lines.
 Each of the remaining lines displays information about a specified cache.
 Following the cache name,
 the output shown in each line shows three components for each cache:
-.IP \(bu 3
+.IP \[bu] 3
 statistics
-.IP \(bu
+.IP \[bu]
 tunables
-.IP \(bu
+.IP \[bu]
 slabdata
 .PP
 The statistics are as follows:
diff --git a/man5/tmpfs.5 b/man5/tmpfs.5
index 1efdbd5fc3..09d9558985 100644
--- a/man5/tmpfs.5
+++ b/man5/tmpfs.5
@@ -27,13 +27,13 @@ $ sudo mount \-t tmpfs \-o size=10M tmpfs /mnt/mytmpfs
 A
 .B tmpfs
 filesystem has the following properties:
-.IP \(bu 3
+.IP \[bu] 3
 The filesystem can employ swap space when physical memory pressure
 demands it.
-.IP \(bu
+.IP \[bu]
 The filesystem consumes only as much physical memory and swap space
 as is required to store the current contents of the filesystem.
-.IP \(bu
+.IP \[bu]
 During a remount operation
 .RI ( "mount\ \-o\ remount" ),
 the filesystem size can be changed
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 /man5
parent	f29fc8dcf0da15a596a7cdc7e5a0b2932100b522 (diff)
download	man-pages-cdede5cdd1b0ba75135d3b32d96354026e96f866.tar.gz