intro.1, localedef.1, memusage.1, memusagestat.1, bpf.2, execve.2, fork.2, keyctl...

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>

diff --git a/man1/intro.1 b/man1/intro.1
index 63fcf5dea91e86003d69a48064d163441e9b969a..10da19f60a31092ee841bb653d42777d5b8dce95 100644 (file)
--- a/man1/intro.1
+++ b/man1/intro.1
@@ -321,5 +321,5 @@ and use a browser if you find HTML files there.
 .BR zsh (1),
 .BR wait (2),
 .BR stdout (3),
-.BR man-pages (7),
+.BR man\-pages (7),
 .BR standards (7)

diff --git a/man1/localedef.1 b/man1/localedef.1
index dcd4ff90d16604fb6bdd7ef3f0180864d0206fd4..756737df8d27c4553bcfabd2a996e3f3e7da0d69 100644 (file)
--- a/man1/localedef.1
+++ b/man1/localedef.1
@@ -187,7 +187,7 @@ are also searched after the current directory.
 The default directory for locale definition files is printed by
 .BR "localedef \-\-help" .
 .TP
-.BI \-u " repertoirefile" "\fR, \fP\-\-repertoire-map=" repertoirefile
+.BI \-u " repertoirefile" "\fR, \fP\-\-repertoire\-map=" repertoirefile
 Read mappings from symbolic names to Unicode code points from
 .IR repertoirefile .
 If

diff --git a/man1/memusage.1 b/man1/memusage.1
index ce50e6f16a27fe46f91bd040b55b68e5f6e2de51..fa1987c79d16a58a012be7813ffc5de2fe722b66 100644 (file)
--- a/man1/memusage.1
+++ b/man1/memusage.1
@@ -152,7 +152,7 @@ Collect
 .I size
 entries before writing them out.
 .TP
-.B \fB\-\-no-timer
+.B \-\-no\-timer
 Disable timer-based
 .RB ( SIGPROF )
 sampling of stack pointer value.

diff --git a/man1/memusagestat.1 b/man1/memusagestat.1
index 809f4ba3e6331250dc6b219fea1d7eae40c1e35c..9426469f5d3517747fb74be41b52cb348820ed98 100644 (file)
--- a/man1/memusagestat.1
+++ b/man1/memusagestat.1
@@ -60,7 +60,7 @@ Use time (rather than number of function calls) as the scale for the X axis.
 .B \-T\fR,\ \fB\-\-total
 Also draw a graph of total memory consumption.
 .TP
-.BI \-x\  size \fR,\ \fB\-\-x-size= size
+.BI \-x\  size \fR,\ \fB\-\-x\-size= size
 Make the output graph
 .I size
 pixels wide.

diff --git a/man2/bpf.2 b/man2/bpf.2
index e386eabbd52df1a23067cb6241d252eb7f34be5b..a3d59e6ac91735672a9bef0476bba1249f8d1d49 100644 (file)
--- a/man2/bpf.2
+++ b/man2/bpf.2
@@ -84,7 +84,7 @@ below for further details.
 Generally, eBPF programs are loaded by the user process and automatically
 unloaded when the process exits.
 In some cases, for example,
-.BR tc-bpf (8),
+.BR tc\-bpf (8),
 the program will continue to stay alive inside the kernel even after the
 process that loaded the program exits.
 In that case,
@@ -1272,10 +1272,10 @@ riscv (since Linux 5.1).
 .PD
 .SH SEE ALSO
 .BR seccomp (2),
-.BR bpf-helpers (7),
+.BR bpf\-helpers (7),
 .BR socket (7),
 .BR tc (8),
-.BR tc-bpf (8)
+.BR tc\-bpf (8)
 .PP
 Both classic and extended BPF are explained in the kernel source file
 .IR Documentation/networking/filter.txt .

diff --git a/man2/execve.2 b/man2/execve.2
index 62becbdd28b0baadfdc4dfdac26f10d677c10a2e..7a8a13414626e60ed0d9b0b46e1f07cdd5b0a685 100644 (file)
--- a/man2/execve.2
+++ b/man2/execve.2
@@ -158,7 +158,7 @@ shared objects.
 This interpreter is typically
 .I /lib/ld-linux.so.2
 for binaries linked with glibc (see
-.BR ld-linux.so (8)).
+.BR ld\-linux.so (8)).
 .\"
 .SS Effect on process attributes
 All process attributes are preserved during an
@@ -857,7 +857,7 @@ program:
 .in +4n
 .EX
 .RB "$" " cat > script"
-.B #!./myecho script-arg
+.B #!./myecho script\-arg
 .B ^D
 .RB "$" " chmod +x script"
 .EE
@@ -869,7 +869,7 @@ We can then use our program to exec the script:
 .EX
 .RB "$" " ./execve ./script"
 argv[0]: ./myecho
-argv[1]: script-arg
+argv[1]: script\-arg
 argv[2]: ./script
 argv[3]: hello
 argv[4]: world

diff --git a/man2/fork.2 b/man2/fork.2
index a48ecabffb96d13ec24bb26ec9cb95b40204a123..7632d2dbe5112d7f792465c0815850a4f0e1724f 100644 (file)
--- a/man2/fork.2
+++ b/man2/fork.2
@@ -177,7 +177,7 @@ After a
 .BR fork ()
 in a multithreaded program,
 the child can safely call only async-signal-safe functions (see
-.BR signal-safety (7))
+.BR signal\-safety (7))
 until such time as it calls
 .BR execve (2).
 .IP *

diff --git a/man2/keyctl.2 b/man2/keyctl.2
index 6d0386c0e08fe6a5d72a8843a1aa0e83eb9479f8..b758f331bd2816529bce18c0ebf4ef879717c22a 100644 (file)
--- a/man2/keyctl.2
+++ b/man2/keyctl.2
@@ -82,27 +82,27 @@ The following values may be specified in
 .B KEY_SPEC_THREAD_KEYRING
 This specifies the calling thread's thread-specific keyring.
 See
-.BR thread-keyring (7).
+.BR thread\-keyring (7).
 .TP
 .B KEY_SPEC_PROCESS_KEYRING
 This specifies the caller's process-specific keyring.
 See
-.BR process-keyring (7).
+.BR process\-keyring (7).
 .TP
 .B KEY_SPEC_SESSION_KEYRING
 This specifies the caller's session-specific keyring.
 See
-.BR session-keyring (7).
+.BR session\-keyring (7).
 .TP
 .B KEY_SPEC_USER_KEYRING
 This specifies the caller's UID-specific keyring.
 See
-.BR user-keyring (7).
+.BR user\-keyring (7).
 .TP
 .B KEY_SPEC_USER_SESSION_KEYRING
 This specifies the caller's UID-session keyring.
 See
-.BR user-session-keyring (7).
+.BR user\-session\-keyring (7).
 .TP
 .BR KEY_SPEC_REQKEY_AUTH_KEY " (since Linux 2.6.16)"
 .\"            commit b5f545c880a2a47947ba2118b2509644ab7a2969
@@ -110,7 +110,7 @@ This specifies the authorization key created by
 .BR request_key (2)
 and passed to the process it spawns to generate a key.
 This key is available only in a
-.BR request-key (8)-style
+.BR request\-key (8)-style
 program that was passed an authorization key by the kernel and
 ceases to be available once the requested key has been instantiated; see
 .BR request_key (2).
@@ -121,7 +121,7 @@ This specifies the key ID for the
 .BR request_key (2)
 destination keyring.
 This keyring is available only in a
-.BR request-key (8)-style
+.BR request\-key (8)-style
 program that was passed an authorization key by the kernel and
 ceases to be available once the requested key has been instantiated; see
 .BR request_key (2).
@@ -875,7 +875,7 @@ The caller must have the appropriate authorization key,
 and once the uninstantiated key has been instantiated,
 the authorization key is revoked.
 In other words, this operation is available only from a
-.BR request-key (8)-style
+.BR request\-key (8)-style
 program.
 See
 .BR request_key (2)
@@ -1070,7 +1070,7 @@ associated with the specified key.
 (In other words, the
 .BR KEYCTL_ASSUME_AUTHORITY
 operation is available only from a
-.BR request-key (8)-style
+.BR request\-key (8)-style
 program; see
 .BR request_key (2)
 for an explanation of how this operation is used.)
@@ -1093,7 +1093,7 @@ and the value 0 is returned.
 The
 .BR KEYCTL_ASSUME_AUTHORITY
 mechanism allows a program such as
-.BR request-key (8)
+.BR request\-key (8)
 to assume the necessary authority to instantiate a new uninstantiated key
 that was created as a consequence of a call to
 .BR request_key (2).
@@ -1249,7 +1249,7 @@ whose ID is specified in
 .IP
 The caller must have the appropriate authorization key.
 In other words, this operation is available only from a
-.BR request-key (8)-style
+.BR request\-key (8)-style
 program.
 See
 .BR request_key (2).
@@ -1258,7 +1258,7 @@ The caller must have the appropriate authorization key,
 and once the uninstantiated key has been instantiated,
 the authorization key is revoked.
 In other words, this operation is available only from a
-.BR request-key (8)-style
+.BR request\-key (8)-style
 program.
 See
 .BR request_key (2)
@@ -1963,7 +1963,7 @@ you probably want to use the various library functions
 mentioned in the descriptions of individual operations above.
 .SH EXAMPLES
 The program below provide subset of the functionality of the
-.BR request-key (8)
+.BR request\-key (8)
 program provided by the
 .I keyutils
 package.
@@ -1973,7 +1973,7 @@ the program records various information in a log file.
 As described in
 .BR request_key (2),
 the
-.BR request-key (8)
+.BR request\-key (8)
 program is invoked with command-line arguments that
 describe a key that is to be instantiated.
 The example program fetches and logs these arguments.
@@ -1983,10 +1983,10 @@ and then instantiates that key.
 The following shell session demonstrates the use of this program.
 In the session,
 we compile the program and then use it to temporarily replace the standard
-.BR request-key (8)
+.BR request\-key (8)
 program.
 (Note that temporarily disabling the standard
-.BR request-key (8)
+.BR request\-key (8)
 program may not be safe on some systems.)
 While our example program is installed,
 we use the example program shown in

diff --git a/man2/request_key.2 b/man2/request_key.2
index 2e88eb50d70e6b06522272396f0e8f7a4691fdb2..e28c11ded9cf22da80ce8531c203c82fd561124f 100644 (file)
--- a/man2/request_key.2
+++ b/man2/request_key.2
@@ -82,23 +82,23 @@ permission, or it may be one of the following special keyring IDs:
 .TP
 .B KEY_SPEC_THREAD_KEYRING
 This specifies the caller's thread-specific keyring (see
-.BR thread-keyring (7)).
+.BR thread\-keyring (7)).
 .TP
 .B KEY_SPEC_PROCESS_KEYRING
 This specifies the caller's process-specific keyring (see
-.BR process-keyring (7)).
+.BR process\-keyring (7)).
 .TP
 .B KEY_SPEC_SESSION_KEYRING
 This specifies the caller's session-specific keyring (see
-.BR session-keyring (7)).
+.BR session\-keyring (7)).
 .TP
 .B KEY_SPEC_USER_KEYRING
 This specifies the caller's UID-specific keyring (see
-.BR user-keyring (7)).
+.BR user\-keyring (7)).
 .TP
 .B KEY_SPEC_USER_SESSION_KEYRING
 This specifies the caller's UID-session keyring (see
-.BR user-session-keyring (7)).
+.BR user\-session\-keyring (7)).
 .PP
 When the
 .I dest_keyring
@@ -132,28 +132,28 @@ since Linux 2.6.29).
 The thread-specific keyring
 .RB ( KEY_REQKEY_DEFL_THREAD_KEYRING ;
 see
-.BR thread-keyring (7)).
+.BR thread\-keyring (7)).
 .IP \(bu
 The process-specific keyring
 .RB ( KEY_REQKEY_DEFL_PROCESS_KEYRING ;
 see
-.BR process-keyring (7)).
+.BR process\-keyring (7)).
 .IP \(bu
 The session-specific keyring
 .RB ( KEY_REQKEY_DEFL_SESSION_KEYRING ;
 see
-.BR session-keyring (7)).
+.BR session\-keyring (7)).
 .IP \(bu
 The session keyring for the process's user ID
 .RB ( KEY_REQKEY_DEFL_USER_SESSION_KEYRING ;
 see
-.BR user-session-keyring (7)).
+.BR user\-session\-keyring (7)).
 This keyring is expected to always exist.
 .IP \(bu
 The UID-specific keyring
 .RB ( KEY_REQKEY_DEFL_USER_KEYRING ;
 see
-.BR user-keyring (7)).
+.BR user\-keyring (7)).
 This keyring is also expected to always exist.
 .\" mtk: Are there circumstances where the user sessions and UID-specific
 .\" keyrings do not exist?
@@ -258,9 +258,9 @@ Internally, the kernel also records the PID of the process that called
 .RE
 .IP c)
 The kernel creates a process that executes a user-space service such as
-.BR request-key (8)
+.BR request\-key (8)
 with a new session keyring that contains a link to the authorization key, V.
-.\" The request-key(8) program can be invoked in circumstances *other* than
+.\" The request\-key(8) program can be invoked in circumstances *other* than
 .\" when triggered by request_key(2). For example, upcalls from places such
 .\" as the DNS resolver.
 .IP
@@ -268,7 +268,7 @@ This program is supplied with the following command-line arguments:
 .RS
 .IP [0] 4
 The string
-.IR """/sbin/request-key""" .
+.IR """/sbin/request\-key""" .
 .IP [1]
 The string
 .I """create"""
@@ -356,7 +356,7 @@ to fail until it does.
 The purpose of this negatively instantiated key is to prevent
 (possibly different) processes making repeated requests
 (that require expensive
-.BR request-key (8)
+.BR request\-key (8)
 upcalls) for a key that can't (at the moment) be positively instantiated.
 .PP
 Once the key has been instantiated, the authorization key
@@ -364,7 +364,7 @@ Once the key has been instantiated, the authorization key
 is revoked, and the destination keyring
 .RB ( KEY_SPEC_REQUESTOR_KEYRING )
 is no longer accessible from the
-.BR request-key (8)
+.BR request\-key (8)
 program.
 .PP
 If a key is created, then\(emregardless of whether it is a valid key or
@@ -458,13 +458,13 @@ The call specifies the session keyring as the target keyring.
 .PP
 In order to demonstrate this program,
 we first create a suitable entry in the file
-.IR /etc/request-key.conf .
+.IR /etc/request\-key.conf .
 .PP
 .in +4n
 .EX
 $ sudo sh
 # \fBecho 'create user mtk:* *   /bin/keyctl instantiate %k %c %S' \e\fP
-          \fB> /etc/request-key.conf\fP
+          \fB> /etc/request\-key.conf\fP
 # \fBexit\fP
 .EE
 .in
@@ -489,7 +489,7 @@ and the session keyring
 of the requestor (i.e., the caller of
 .BR request_key ()).
 See
-.BR request-key.conf (5)
+.BR request\-key.conf (5)
 for details of these
 .I %
 specifiers.
@@ -502,7 +502,7 @@ to verify that the requested key has been instantiated:
 .EX
 $ \fB./t_request_key user mtk:key1 "Payload data"\fP
 $ \fBgrep \(aq2dddaf50\(aq /proc/keys\fP
-2dddaf50 I--Q---  1 perm 3f010000  1000  1000 user  mtk:key1: 12
+2dddaf50 I\-\-Q\-\-\-  1 perm 3f010000  1000  1000 user  mtk:key1: 12
 .EE
 .in
 .PP

diff --git a/man2/sigaction.2 b/man2/sigaction.2
index 294a96b63acf3579df9b30545080de3ed0af8050..21d8b15b394ee38ff1bf277a8f78397d2d213f93 100644 (file)
--- a/man2/sigaction.2
+++ b/man2/sigaction.2
@@ -945,7 +945,7 @@ See
 for details on manipulating signal sets.
 .PP
 See
-.BR signal-safety (7)
+.BR signal\-safety (7)
 for a list of the async-signal-safe functions that can be
 safely called inside from inside a signal handler.
 .\"

diff --git a/man2/signal.2 b/man2/signal.2
index c79349918cf8ac0a0ebbd4fa2095f1a38fc71e95..dbe5baa5e25ba8f1a2baeca88f5ef7bdc4c34cd3 100644 (file)
--- a/man2/signal.2
+++ b/man2/signal.2
@@ -140,7 +140,7 @@ is set to
 .BR SIG_IGN .
 .PP
 See
-.BR signal-safety (7)
+.BR signal\-safety (7)
 for a list of the async-signal-safe functions that can be
 safely called from inside a signal handler.
 .PP

diff --git a/man2/socket.2 b/man2/socket.2
index 1d95f4080a9ae2ae8166647c93da248471d18fb0..7908f4fc8fee4d1770d4c1b22880cc9260fa66f1 100644 (file)
--- a/man2/socket.2
+++ b/man2/socket.2
@@ -146,7 +146,7 @@ T}:T{
 .\" rds-tools: https://github.com/oracle/rds-tools/blob/master/rds-rdma.7
 .BR rds (7)
 .br
-.BR rds-rdma (7)
+.BR rds\-rdma (7)
 T}
 T{
 .B AF_PPPOX

diff --git a/man3/dlopen.3 b/man3/dlopen.3
index 3b21e8257c0efefbdf9361aba6b657fd47a3482d..8e18f70c077dfb2360d1742a23f88e7d76af897a 100644 (file)
--- a/man3/dlopen.3
+++ b/man3/dlopen.3
@@ -622,7 +622,7 @@ main(void)
 .BR dlerror (3),
 .BR dlinfo (3),
 .BR dlsym (3),
-.BR rtld-audit (7),
+.BR rtld\-audit (7),
 .BR ld.so (8),
 .BR ldconfig (8)
 .PP

diff --git a/man3/getauxval.3 b/man3/getauxval.3
index 2b7b1f270fbcec5457ce71b0d9e6b5c4077c6870..c8643ebc74b143764c6829cb0bc9bd5a0ceb4c7b 100644 (file)
--- a/man3/getauxval.3
+++ b/man3/getauxval.3
@@ -192,7 +192,7 @@ Alternatively,
 a nonzero value may be triggered by a Linux Security Module.
 When this value is nonzero,
 the dynamic linker disables the use of certain environment variables (see
-.BR ld-linux.so (8))
+.BR ld\-linux.so (8))
 and glibc changes other aspects of its behavior.
 (See also
 .BR secure_getenv (3).)
@@ -247,7 +247,7 @@ This function is a nonstandard glibc extension.
 .SH NOTES
 The primary consumer of the information in the auxiliary vector
 is the dynamic linker,
-.BR ld-linux.so (8).
+.BR ld\-linux.so (8).
 The auxiliary vector is a convenient and efficient shortcut
 that allows the kernel to communicate a certain set of standard
 information that the dynamic linker usually or always needs.
@@ -284,4 +284,4 @@ was zero.
 .SH SEE ALSO
 .BR secure_getenv (3),
 .BR vdso (7),
-.BR ld-linux.so (8)
+.BR ld\-linux.so (8)

diff --git a/man3/gnu_get_libc_version.3 b/man3/gnu_get_libc_version.3
index 42826a674f8c5f942340d4347eb82f22336135ca..4aa9fe7528d63d4eca41c603c426d9c0e387d23e 100644 (file)
--- a/man3/gnu_get_libc_version.3
+++ b/man3/gnu_get_libc_version.3
@@ -28,7 +28,7 @@
 gnu_get_libc_version, gnu_get_libc_release \- get glibc version and release
 .SH SYNOPSIS
 .nf
-.B #include <gnu/libc-version.h>
+.B #include <gnu/libc\-version.h>
 .PP
 .B const char *gnu_get_libc_version(void);
 .B const char *gnu_get_libc_release(void);

diff --git a/man3/pthread_atfork.3 b/man3/pthread_atfork.3
index 2d480bd7e90a926ac5862d393970591e923067fd..ac517d0f395864d966574ea92814b45720abea70 100644 (file)
--- a/man3/pthread_atfork.3
+++ b/man3/pthread_atfork.3
@@ -111,7 +111,7 @@ After a
 .BR fork (2)
 in a multithreaded process returns in the child,
 the child should call only async-signal-safe functions (see
-.BR signal-safety (7))
+.BR signal\-safety (7))
 until such time as it calls
 .BR execve (2)
 to execute a new program.

diff --git a/man3/sem_post.3 b/man3/sem_post.3
index 2f1b53320d304abe4826d9e0a407c18a407c0b04..69b970b7c522af9b49973528fb03732f531f7fe5 100644 (file)
--- a/man3/sem_post.3
+++ b/man3/sem_post.3
@@ -85,4 +85,4 @@ and
 .BR sem_getvalue (3),
 .BR sem_wait (3),
 .BR sem_overview (7),
-.BR signal-safety (7)
+.BR signal\-safety (7)

diff --git a/man3/setjmp.3 b/man3/setjmp.3
index c456681b13f16423dcfcebf5e66265947cd7b64d..828d663f6674a11723326cae53f0f73c673bd7f5 100644 (file)
--- a/man3/setjmp.3
+++ b/man3/setjmp.3
@@ -324,4 +324,4 @@ returning from the initial call to
 .IR main ().
 .SH SEE ALSO
 .BR signal (7),
-.BR signal-safety (7)
+.BR signal\-safety (7)

diff --git a/man3/strftime.3 b/man3/strftime.3
index ce4ac62709f2d63d6e246808684d79fca0628a19..62625673d06810099c1606a5ebf505dbf73ef20b 100644 (file)
--- a/man3/strftime.3
+++ b/man3/strftime.3
@@ -177,7 +177,7 @@ Modifier: use alternative ("era-based") format, see below. (SU)
 .TP
 .B %F
 Equivalent to
-.B %Y-%m-%d
+.B %Y\-%m\-%d
 (the ISO\ 8601 date format). (C99)
 .TP
 .B %G

diff --git a/man4/veth.4 b/man4/veth.4
index 97f596844df926ca351c947d92e7ed16f5875d5b..a726c86720da43c37f82c7215a8d70e58ff17e07 100644 (file)
--- a/man4/veth.4
+++ b/man4/veth.4
@@ -103,5 +103,5 @@ NIC statistics:
 .BR clone (2),
 .BR network_namespaces (7),
 .BR ip (8),
-.BR ip-link (8),
-.BR ip-netns (8)
+.BR ip\-link (8),
+.BR ip\-netns (8)

diff --git a/man5/locale.5 b/man5/locale.5
index a2f6b96c94e9fbcbe9f60e92915fb58230812673..85e548bc17f32ffdae5e1e1e64aa4fdff1973701 100644 (file)
--- a/man5/locale.5
+++ b/man5/locale.5
@@ -1328,4 +1328,4 @@ Monday for the locale.
 .BR charsets (7),
 .BR locale (7),
 .BR unicode (7),
-.BR utf-8 (7)
+.BR utf\-8 (7)

diff --git a/man5/nscd.conf.5 b/man5/nscd.conf.5
index 5da2a4b49c25e74ee180f62c85d78c7889a2817d..40bde4238be8f8d2570fd7e380ff1be38d46f72a 100644 (file)
--- a/man5/nscd.conf.5
+++ b/man5/nscd.conf.5
@@ -43,7 +43,7 @@ or \fInetgroup\fP.
 Specifies name of the file to which debug info should be written.
 .RE
 .PP
-.B debug-level
+.B debug\-level
 .I value
 .RS
 Sets the desired debug level.
@@ -58,14 +58,14 @@ requests.
 At least five threads will always be created.
 .RE
 .PP
-.B max-threads
+.B max\-threads
 .I number
 .RS
 Specifies the maximum number of threads.
 The default is 32.
 .RE
 .PP
-.B server-user
+.B server\-user
 .I user
 .RS
 If this option is set, nscd will run as this user and not as root.
@@ -73,13 +73,13 @@ If a separate cache for every user is used (\-S parameter), this
 option is ignored.
 .RE
 .PP
-.B stat-user
+.B stat\-user
 .I user
 .RS
 Specifies the user who is allowed to request statistics.
 .RE
 .PP
-.B reload-count
+.B reload\-count
 unlimited |
 .I number
 .RS
@@ -95,7 +95,7 @@ Enabling paranoia mode causes nscd to restart itself periodically.
 The default is no.
 .RE
 .PP
-.B restart-interval
+.B restart\-interval
 .I time
 .RS
 Sets the restart interval to
@@ -107,7 +107,7 @@ mode.
 The default is 3600.
 .RE
 .PP
-.B enable-cache
+.B enable\-cache
 .I service
 .I <yes|no>
 .RS
@@ -117,7 +117,7 @@ cache.
 The default is no.
 .RE
 .PP
-.B positive-time-to-live
+.B positive\-time\-to\-live
 .I service
 .I value
 .RS
@@ -130,7 +130,7 @@ Larger values increase cache hit rates and reduce mean
 response times, but increase problems with cache coherence.
 .RE
 .PP
-.B negative-time-to-live
+.B negative\-time\-to\-live
 .I service
 .I value
 .RS
@@ -145,7 +145,7 @@ example untarring the Linux kernel sources as root); should be kept small
 to reduce cache coherency problems.
 .RE
 .PP
-.B suggested-size
+.B suggested\-size
 .I service
 .I value
 .RS
@@ -155,7 +155,7 @@ should remain a prime number for optimum efficiency.
 The default is 211.
 .RE
 .PP
-.B check-files
+.B check\-files
 .I service
 .I <yes|no>
 .RS
@@ -196,7 +196,7 @@ daemon over the socket each time a lookup is performed.
 The default is no.
 .RE
 .PP
-.B max-db-size
+.B max\-db\-size
 .I service
 .I bytes
 .RS
@@ -205,7 +205,7 @@ The maximum allowable size, in bytes, of the database files for the
 The default is 33554432.
 .RE
 .PP
-.B auto-propagate
+.B auto\-propagate
 .I service
 .I <yes|no>
 .RS

diff --git a/man5/resolv.conf.5 b/man5/resolv.conf.5
index 6b9c31b9a95ec239432d6d6f8303f82ebd292d58..67c99a64a250ae8919583948554af485a6337eaf 100644 (file)
--- a/man5/resolv.conf.5
+++ b/man5/resolv.conf.5
@@ -251,7 +251,7 @@ reverse IPv6 lookups are made in the
 .I ip6.arpa
 zone by default.
 These options are available in glibc versions up to 2.24, where
-.BR no-ip6-dotint
+.BR no\-ip6\-dotint
 is the default.
 Since
 .BR ip6\-dotint

diff --git a/man7/address_families.7 b/man7/address_families.7
index feaadf0891c6ef179f4e6ecfa5f8d40b2317c52b..c68324f7e22713c70cf11e6cc4a866228e0a1d93 100644 (file)
--- a/man7/address_families.7
+++ b/man7/address_families.7
@@ -194,7 +194,7 @@ For further information see
 .\" rds-tools: https://github.com/oracle/rds-tools/blob/master/rds.7
 .\" rds-tools: https://github.com/oracle/rds-tools/blob/master/rds-rdma.7
 .BR rds (7),
-.BR rds-rdma (7),
+.BR rds\-rdma (7),
 and
 .I Documentation/networking/rds.txt
 in the Linux kernel source tree.

diff --git a/man7/armscii-8.7 b/man7/armscii-8.7
index 9ee2341a02a9295c29558e2866c0bc782a9fc03d..94c51e3680c01793e151468fd8ea9131db31e2d5 100644 (file)
--- a/man7/armscii-8.7
+++ b/man7/armscii-8.7
@@ -136,4 +136,4 @@ _
 .SH SEE ALSO
 .BR ascii (7),
 .BR charsets (7),
-.BR utf-8 (7)
+.BR utf\-8 (7)

diff --git a/man7/ascii.7 b/man7/ascii.7
index 8780c48f968c499b4f5c89e4b972de5194351ac5..11b311f9d42c454662dbdd8801494951ac394ad2 100644 (file)
--- a/man7/ascii.7
+++ b/man7/ascii.7
@@ -184,19 +184,19 @@ Standards Institute (USASI) in 1968.
 .\"
 .SH SEE ALSO
 .BR charsets (7),
-.BR iso_8859-1 (7),
-.BR iso_8859-2 (7),
-.BR iso_8859-3 (7),
-.BR iso_8859-4 (7),
-.BR iso_8859-5 (7),
-.BR iso_8859-6 (7),
-.BR iso_8859-7 (7),
-.BR iso_8859-8 (7),
-.BR iso_8859-9 (7),
-.BR iso_8859-10 (7),
-.BR iso_8859-11 (7),
-.BR iso_8859-13 (7),
-.BR iso_8859-14 (7),
-.BR iso_8859-15 (7),
-.BR iso_8859-16 (7),
-.BR utf-8 (7)
+.BR iso_8859\-1 (7),
+.BR iso_8859\-2 (7),
+.BR iso_8859\-3 (7),
+.BR iso_8859\-4 (7),
+.BR iso_8859\-5 (7),
+.BR iso_8859\-6 (7),
+.BR iso_8859\-7 (7),
+.BR iso_8859\-8 (7),
+.BR iso_8859\-9 (7),
+.BR iso_8859\-10 (7),
+.BR iso_8859\-11 (7),
+.BR iso_8859\-13 (7),
+.BR iso_8859\-14 (7),
+.BR iso_8859\-15 (7),
+.BR iso_8859\-16 (7),
+.BR utf\-8 (7)

diff --git a/man7/capabilities.7 b/man7/capabilities.7
index d7c50f716b6efd8b088e0033418abe640708f704..fd841b4f16b39338c0d747d91bc151452da2e22a 100644 (file)
--- a/man7/capabilities.7
+++ b/man7/capabilities.7
@@ -94,7 +94,7 @@ Employ features that can block system suspend
 Employ privileged BPF operations; see
 .BR bpf (2)
 and
-.BR bpf-helpers (7).
+.BR bpf\-helpers (7).
 .IP
 This capability was added in Linux 5.8 to separate out
 BPF functionality from the overloaded

diff --git a/man7/cgroups.7 b/man7/cgroups.7
index 5d060c2ada23afb231b8a36e2c27169d7c22b4cf..59598016aba0b037c49c1617333c3ebbe81aaaea 100644 (file)
--- a/man7/cgroups.7
+++ b/man7/cgroups.7
@@ -1914,8 +1914,8 @@ mount option.
 .SH SEE ALSO
 .BR prlimit (1),
 .BR systemd (1),
-.BR systemd-cgls (1),
-.BR systemd-cgtop (1),
+.BR systemd\-cgls (1),
+.BR systemd\-cgtop (1),
 .BR clone (2),
 .BR ioprio_set (2),
 .BR perf_event_open (2),

diff --git a/man7/charsets.7 b/man7/charsets.7
index 95085e4844b1b04b847b3b5ca30c05ac899c0e93..439ea7343708920eb95462f055c1a8ed38ff38d0 100644 (file)
--- a/man7/charsets.7
+++ b/man7/charsets.7
@@ -330,6 +330,6 @@ Korean, but it is enough for most other purposes.
 .SH SEE ALSO
 .BR iconv (1),
 .BR ascii (7),
-.BR iso_8859-1 (7),
+.BR iso_8859\-1 (7),
 .BR unicode (7),
-.BR utf-8 (7)
+.BR utf\-8 (7)

diff --git a/man7/cp1251.7 b/man7/cp1251.7
index 4d48fd138bf7b710676fad2d334a3b98a74371d2..382de42c85105bc14954e5a75cfff9b0df62ff56 100644 (file)
--- a/man7/cp1251.7
+++ b/man7/cp1251.7
@@ -179,7 +179,7 @@ CP\ 1251 is also known as Windows Cyrillic.
 .BR ascii (7),
 .BR charsets (7),
 .BR cp1252 (7),
-.BR iso_8859-5 (7),
-.BR koi8-r (7),
-.BR koi8-u (7),
-.BR utf-8 (7)
+.BR iso_8859\-5 (7),
+.BR koi8\-r (7),
+.BR koi8\-u (7),
+.BR utf\-8 (7)

diff --git a/man7/cp1252.7 b/man7/cp1252.7
index 013acc53ff0f0d37f35b8ce0ba21454da94332d3..07ac84bf5d19cbed1b1d6a528724d6d3adb0c8ce 100644 (file)
--- a/man7/cp1252.7
+++ b/man7/cp1252.7
@@ -170,6 +170,6 @@ CP\ 1252 is also known as Windows-1252.
 .BR ascii (7),
 .BR charsets (7),
 .BR cp1251 (7),
-.BR iso_8859-1 (7),
-.BR iso_8859-15 (7),
-.BR utf-8 (7)
+.BR iso_8859\-1 (7),
+.BR iso_8859\-15 (7),
+.BR utf\-8 (7)

diff --git a/man7/iso_8859-1.7 b/man7/iso_8859-1.7
index 5607545b99faebd525f9a9d5422c5af269ee6b26..202768231f51481d8e17f01d5e6eb5b47ef920f2 100644 (file)
--- a/man7/iso_8859-1.7
+++ b/man7/iso_8859-1.7
@@ -165,5 +165,5 @@ ISO 8859-1 is also known as Latin-1.
 .BR ascii (7),
 .BR charsets (7),
 .BR cp1252 (7),
-.BR iso_8859-15 (7),
-.BR utf-8 (7)
+.BR iso_8859\-15 (7),
+.BR utf\-8 (7)

diff --git a/man7/iso_8859-10.7 b/man7/iso_8859-10.7
index f299fb43c0a5a4369c69198ba7230e9673e24a09..82c8eeda5f7f9639ab958033244cfdb40d2d39a6 100644 (file)
--- a/man7/iso_8859-10.7
+++ b/man7/iso_8859-10.7
@@ -162,4 +162,4 @@ ISO 8859-10 is also known as Latin-6.
 .SH SEE ALSO
 .BR ascii (7),
 .BR charsets (7),
-.BR utf-8 (7)
+.BR utf\-8 (7)

diff --git a/man7/iso_8859-11.7 b/man7/iso_8859-11.7
index 2147ff3a714f2f5ed245d3bef2340169bc550aa0..073ddc65771ee23832008e95154035f6a01b5337 100644 (file)
--- a/man7/iso_8859-11.7
+++ b/man7/iso_8859-11.7
@@ -159,4 +159,4 @@ while TIS-620 leaves it undefined.
 .SH SEE ALSO
 .BR ascii (7),
 .BR charsets (7),
-.BR utf-8 (7)
+.BR utf\-8 (7)

diff --git a/man7/iso_8859-13.7 b/man7/iso_8859-13.7
index 030de5414efbd6284b032b1408130ef5a1568320..06de48839aa80790f86110ecc39253934d4a125f 100644 (file)
--- a/man7/iso_8859-13.7
+++ b/man7/iso_8859-13.7
@@ -162,4 +162,4 @@ ISO 8859-13 is also known as Latin-7.
 .SH SEE ALSO
 .BR ascii (7),
 .BR charsets (7),
-.BR utf-8 (7)
+.BR utf\-8 (7)

diff --git a/man7/iso_8859-14.7 b/man7/iso_8859-14.7
index 3a0d2cdee878979f1717a40dce830ea21623c3bd..592bd0838e05020cd292be36e141cb04a5a5a481 100644 (file)
--- a/man7/iso_8859-14.7
+++ b/man7/iso_8859-14.7
@@ -162,4 +162,4 @@ ISO 8859-14 is also known as Latin-8.
 .SH SEE ALSO
 .BR ascii (7),
 .BR charsets (7),
-.BR utf-8 (7)
+.BR utf\-8 (7)

diff --git a/man7/iso_8859-15.7 b/man7/iso_8859-15.7
index 1bf9aa7f2b46b73b55a44f1926f65080ea1c8331..5e71a41aae60d03dda13e475e4cfb14796712ef0 100644 (file)
--- a/man7/iso_8859-15.7
+++ b/man7/iso_8859-15.7
@@ -164,5 +164,5 @@ ISO 8859-15 is also known as Latin-9 (or sometimes as Latin-0).
 .BR ascii (7),
 .BR charsets (7),
 .BR cp1252 (7),
-.BR iso_8859-1 (7),
-.BR utf-8 (7)
+.BR iso_8859\-1 (7),
+.BR utf\-8 (7)

diff --git a/man7/iso_8859-16.7 b/man7/iso_8859-16.7
index 991fc13b1dfd8fbdc9905ba179d31715e32b6066..8d9b5a2595860477e82a14f543e2261ceaec998b 100644 (file)
--- a/man7/iso_8859-16.7
+++ b/man7/iso_8859-16.7
@@ -162,5 +162,5 @@ ISO 8859-16 is also known as Latin-10.
 .SH SEE ALSO
 .BR ascii (7),
 .BR charsets (7),
-.BR iso_8859-3 (7),
-.BR utf-8 (7)
+.BR iso_8859\-3 (7),
+.BR utf\-8 (7)

diff --git a/man7/iso_8859-2.7 b/man7/iso_8859-2.7
index 2b3863bba1f2100e431afdbec4ce600ca651060d..095f0612d0caf2c51dcd52f6738e1ff40ce2fbff 100644 (file)
--- a/man7/iso_8859-2.7
+++ b/man7/iso_8859-2.7
@@ -165,6 +165,6 @@ ISO 8859-2 is also known as Latin-2.
 .SH SEE ALSO
 .BR ascii (7),
 .BR charsets (7),
-.BR iso_8859-1 (7),
-.BR iso_8859-16 (7),
-.BR utf-8 (7)
+.BR iso_8859\-1 (7),
+.BR iso_8859\-16 (7),
+.BR utf\-8 (7)

diff --git a/man7/iso_8859-3.7 b/man7/iso_8859-3.7
index fe7d60d10448e3abb13e374d6ccfb3b0dedc0bb2..5f2605852f3d78b43642bde6e020d0f228c13f2f 100644 (file)
--- a/man7/iso_8859-3.7
+++ b/man7/iso_8859-3.7
@@ -155,4 +155,4 @@ ISO 8859-3 is also known as Latin-3.
 .SH SEE ALSO
 .BR ascii (7),
 .BR charsets (7),
-.BR utf-8 (7)
+.BR utf\-8 (7)

diff --git a/man7/iso_8859-4.7 b/man7/iso_8859-4.7
index ec3d5d2e5e1f5e067230b0c7fc5600626fb70d1d..6eefaef93989d7620c5c2b709bbf298a969914e5 100644 (file)
--- a/man7/iso_8859-4.7
+++ b/man7/iso_8859-4.7
@@ -162,4 +162,4 @@ ISO 8859-4 is also known as Latin-4.
 .SH SEE ALSO
 .BR ascii (7),
 .BR charsets (7),
-.BR utf-8 (7)
+.BR utf\-8 (7)

diff --git a/man7/iso_8859-5.7 b/man7/iso_8859-5.7
index 4a4933613b8194b86d7d035d0e5c0d539475c01c..7e3c8cec108737b415e17654281efaed186a5d8c 100644 (file)
--- a/man7/iso_8859-5.7
+++ b/man7/iso_8859-5.7
@@ -165,6 +165,6 @@ T}
 .BR ascii (7),
 .BR charsets (7),
 .BR cp1251 (7),
-.BR koi8-r (7),
-.BR koi8-u (7),
-.BR utf-8 (7)
+.BR koi8\-r (7),
+.BR koi8\-u (7),
+.BR utf\-8 (7)

diff --git a/man7/iso_8859-6.7 b/man7/iso_8859-6.7
index 8f52e7b61f9622d4e198e8b13e658632bc79ca5a..5e1608a2e342fb2f65144f785c46e52407d34fd6 100644 (file)
--- a/man7/iso_8859-6.7
+++ b/man7/iso_8859-6.7
@@ -118,4 +118,4 @@ such as Urdu and Persian (Farsi).
 .SH SEE ALSO
 .BR ascii (7),
 .BR charsets (7),
-.BR utf-8 (7)
+.BR utf\-8 (7)

diff --git a/man7/iso_8859-7.7 b/man7/iso_8859-7.7
index 3ede304553d24676258df6adb1a1988c42b42a06..f5957088808915e7098840c45f5a91ad907a97a0 100644 (file)
--- a/man7/iso_8859-7.7
+++ b/man7/iso_8859-7.7
@@ -166,4 +166,4 @@ ISO 8859-7 was formerly known as ELOT-928 or ECMA-118:1986.
 .SH SEE ALSO
 .BR ascii (7),
 .BR charsets (7),
-.BR utf-8 (7)
+.BR utf\-8 (7)

diff --git a/man7/iso_8859-8.7 b/man7/iso_8859-8.7
index c1d294ea042b55fac7f490675d4276528e8d2abf..b7e1c5f7b53ab1770b986855aab16db713d5c962 100644 (file)
--- a/man7/iso_8859-8.7
+++ b/man7/iso_8859-8.7
@@ -130,4 +130,4 @@ and Yiddish is not provided for.
 .SH SEE ALSO
 .BR ascii (7),
 .BR charsets (7),
-.BR utf-8 (7)
+.BR utf\-8 (7)

diff --git a/man7/iso_8859-9.7 b/man7/iso_8859-9.7
index 78184d6210bddc54b34cabc1c231dead82e1843f..b97efc29cf15780f029235b771406ccc7c844d6e 100644 (file)
--- a/man7/iso_8859-9.7
+++ b/man7/iso_8859-9.7
@@ -162,4 +162,4 @@ ISO 8859-9 is also known as Latin-5.
 .SH SEE ALSO
 .BR ascii (7),
 .BR charsets (7),
-.BR utf-8 (7)
+.BR utf\-8 (7)

diff --git a/man7/keyrings.7 b/man7/keyrings.7
index e943cd4b86d02c8e9e64aca420ec8d48cc33fa47..0e0bd0a9514a2bce5ac6defb5ebc7c049c67a2bb 100644 (file)
--- a/man7/keyrings.7
+++ b/man7/keyrings.7
@@ -235,13 +235,13 @@ which is usually as long as the process exists.
 .IP
 There are three keyrings with different inheritance/sharing rules:
 the
-.BR session-keyring (7)
+.BR session\-keyring (7)
 (inherited and shared by all child processes),
 the
-.BR process-keyring (7)
+.BR process\-keyring (7)
 (shared by all threads in a process) and
 the
-.BR thread-keyring (7)
+.BR thread\-keyring (7)
 (specific to a particular thread).
 .IP
 As an alternative to using the actual keyring IDs,
@@ -259,9 +259,9 @@ can be used to refer to the caller's own instances of these keyrings.
 .TP
 User keyrings
 Each UID known to the kernel has a record that contains two keyrings: the
-.BR user-keyring (7)
+.BR user\-keyring (7)
 and the
-.BR user-session-keyring (7).
+.BR user\-session\-keyring (7).
 These exist for as long as the UID record in the kernel exists.
 .IP
 As an alternative to using the actual keyring IDs,
@@ -282,7 +282,7 @@ when a new login session is initiated.
 .TP
 Persistent keyrings
 There is a
-.BR persistent-keyring (7)
+.BR persistent\-keyring (7)
 available to each UID known to the system.
 It may persist beyond the life of the UID record previously mentioned,
 but has an expiration time set such that it is automatically cleaned up
@@ -321,10 +321,10 @@ Any key or keyring that does not grant
 permission to the caller is ignored in all the following rules.
 .IP (2)
 A thread possesses its
-.BR session-keyring (7),
-.BR process-keyring (7),
+.BR session\-keyring (7),
+.BR process\-keyring (7),
 and
-.BR thread-keyring (7)
+.BR thread\-keyring (7)
 directly because those keyrings are referred to by its credentials.
 .IP (3)
 If a keyring is possessed, then any key it links to is also possessed.
@@ -349,7 +349,7 @@ on the basis of UID and GID matches.
 When it creates the session keyring,
 .BR pam_keyinit (8)
 adds a link to the
-.BR user-keyring (7),
+.BR user\-keyring (7),
 thus making the user keyring and anything it contains possessed by default.
 .\"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
 .SS Access rights
@@ -448,13 +448,13 @@ for use by internal components that make use of keys.)
 The search algorithm works as follows:
 .IP (1) 4
 The process keyrings are searched in the following order: the thread
-.BR thread-keyring (7)
+.BR thread\-keyring (7)
 if it exists, the
-.BR process-keyring (7)
+.BR process\-keyring (7)
 if it exists, and then either the
-.BR session-keyring (7)
+.BR session\-keyring (7)
 if it exists or the
-.BR user-session-keyring (7)
+.BR user\-session\-keyring (7)
 if that exists.
 .IP (2)
 If the caller was a process that was invoked by the
@@ -498,7 +498,7 @@ This allows keys to be created on an as-needed basis.
 .PP
 Typically,
 this will involve the kernel creating a new process that executes the
-.BR request-key (8)
+.BR request\-key (8)
 program, which will then execute the appropriate handler based on its
 configuration.
 .PP
@@ -513,9 +513,9 @@ See
 .BR keyctl_instantiate (3),
 .BR keyctl_negate (3),
 .BR keyctl_reject (3),
-.BR request-key (8),
+.BR request\-key (8),
 and
-.BR request-key.conf (5)
+.BR request\-key.conf (5)
 for more information.
 .\"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
 .SS /proc files
@@ -592,7 +592,7 @@ The key contributes to the user's quota.
 .\" KEY_FLAG_USER_CONSTRUCT
 The key is under construction via a callback to user space;
 see
-.BR request-key (2).
+.BR request\-key (2).
 .IP N
 .\" KEY_FLAG_NEGATIVE
 The key is negatively instantiated.
@@ -875,7 +875,7 @@ scripts can use them.
 .BR user\-keyring (7),
 .BR user\-session\-keyring (7),
 .BR pam_keyinit (8),
-.BR request-key (8)
+.BR request\-key (8)
 .PP
 The kernel source files
 .IR Documentation/crypto/asymmetric-keys.txt

diff --git a/man7/koi8-r.7 b/man7/koi8-r.7
index 140521eb348820a5e676338bec53a117257f18e1..7ee9e2927d42fa55b1c8b23ea67b5ee4a47cbab7 100644 (file)
--- a/man7/koi8-r.7
+++ b/man7/koi8-r.7
@@ -183,6 +183,6 @@ A4, A6, A7, AD, B4, B6, B7, and BD.
 .BR ascii (7),
 .BR charsets (7),
 .BR cp1251 (7),
-.BR iso_8859-5 (7),
-.BR koi8-u (7),
-.BR utf-8 (7)
+.BR iso_8859\-5 (7),
+.BR koi8\-u (7),
+.BR utf\-8 (7)

diff --git a/man7/koi8-u.7 b/man7/koi8-u.7
index 55e8766c6d119793aefa9b2c227f5cd092acbd0b..0c56e949f3e4655c5dc7700c590705e08a540817 100644 (file)
--- a/man7/koi8-u.7
+++ b/man7/koi8-u.7
@@ -189,6 +189,6 @@ A4, A6, A7, AD, B4, B6, B7, and BD.
 .BR ascii (7),
 .BR charsets (7),
 .BR cp1251 (7),
-.BR iso_8859-5 (7),
-.BR koi8-r (7),
-.BR utf-8 (7)
+.BR iso_8859\-5 (7),
+.BR koi8\-r (7),
+.BR utf\-8 (7)

diff --git a/man7/libc.7 b/man7/libc.7
index 66b06a2671eb335e27803f56e877de556085aefc..2809a97cee2f0f3af0a0cfdcbeba94fd88c03930 100644 (file)
--- a/man7/libc.7
+++ b/man7/libc.7
@@ -117,6 +117,6 @@ project, where they are known.
 .BR getauxval (3),
 .BR proc (5),
 .BR feature_test_macros (7),
-.BR man-pages (7),
+.BR man\-pages (7),
 .BR standards (7),
 .BR vdso (7)

diff --git a/man7/locale.7 b/man7/locale.7
index d8da47c31e8e6bbe1f7b91c2acd53d17f8c3ebd2..ca3f05725d8229f5722c6cede1172b3819f34284 100644 (file)
--- a/man7/locale.7
+++ b/man7/locale.7
@@ -397,4 +397,4 @@ POSIX.1-2001.
 .BR locale (5),
 .BR charsets (7),
 .BR unicode (7),
-.BR utf-8 (7)
+.BR utf\-8 (7)

diff --git a/man7/man.7 b/man7/man.7
index 43bd0b9622d20dd0ae759dbaf84ca80d8a4d0e57..559d40db65e4e1126ace9cf9945c7300e94a42a1 100644 (file)
--- a/man7/man.7
+++ b/man7/man.7
@@ -74,7 +74,7 @@ macro package is in use.
 .PP
 For conventions that should be employed when writing man pages
 for the Linux \fIman-pages\fP package, see
-.BR man-pages (7).
+.BR man\-pages (7).
 .SS Title line
 The first command in a man page (after comment lines,
 that is, lines that start with \fB.\e"\fP) should be
@@ -87,7 +87,7 @@ that is, lines that start with \fB.\e"\fP) should be
 For details of the arguments that should be supplied to the
 .B TH
 command, see
-.BR man-pages (7).
+.BR man\-pages (7).
 .PP
 Note that BSD mdoc-formatted pages begin with the
 .B Dd
@@ -127,7 +127,7 @@ commands.
 for further details on the syntax of the NAME section.)
 .PP
 For a list of other sections that might appear in a manual page, see
-.BR man-pages (7).
+.BR man\-pages (7).
 .SS Fonts
 The commands to select the type face are:
 .TP 4
@@ -520,5 +520,5 @@ is not implemented.
 .BR whatis (1),
 .BR groff_man (7),
 .BR groff_www (7),
-.BR man-pages (7),
+.BR man\-pages (7),
 .BR mdoc (7)

diff --git a/man7/network_namespaces.7 b/man7/network_namespaces.7
index e227ece50493d8f8f66dbf6aa477b50b0aa077fd..aa1b045895a9ec116381af32f14cd493e357f3f5 100644 (file)
--- a/man7/network_namespaces.7
+++ b/man7/network_namespaces.7
@@ -74,8 +74,8 @@ option.
 .BR user_namespaces (7),
 .BR brctl (8),
 .BR ip (8),
-.BR ip-address (8),
-.BR ip-link (8),
-.BR ip-netns (8),
+.BR ip\-address (8),
+.BR ip\-link (8),
+.BR ip\-netns (8),
 .BR iptables (8),
-.BR ovs-vsctl (8)
+.BR ovs\-vsctl (8)

diff --git a/man7/persistent-keyring.7 b/man7/persistent-keyring.7
index 46e92231e3b8a55f9cbceb451347dfdd40f7705f..3367ec153f47bb1e55d170dcb75a4b0d746b35cc 100644 (file)
--- a/man7/persistent-keyring.7
+++ b/man7/persistent-keyring.7
@@ -67,9 +67,9 @@ at which point it is garbage collected.
 This allows the persistent keyring to carry keys beyond the life of
 the kernel's record of the corresponding UID
 (the destruction of which results in the destruction of the
-.BR user-keyring (7)
+.BR user\-keyring (7)
 and the
-.BR user-session-keyring (7)).
+.BR user\-session\-keyring (7)).
 The persistent keyring can thus be used to
 hold authentication tokens for processes that run without user interaction,
 such as programs started by

diff --git a/man7/session-keyring.7 b/man7/session-keyring.7
index 3b9a008708cdef61dd0ec08a1ec77567361d0b1d..0b886be5e7020c6de14e297b4f693063ebb4bdff 100644 (file)
--- a/man7/session-keyring.7
+++ b/man7/session-keyring.7
@@ -17,7 +17,7 @@ The session keyring is a keyring used to anchor keys on behalf of a process.
 It is typically created by
 .BR pam_keyinit (8)
 when a user logs in and a link will be added that refers to the
-.BR user-keyring (7).
+.BR user\-keyring (7).
 Optionally, PAM may revoke the session keyring on logout.
 (In typical configurations, PAM does do this revocation.)
 The session keyring has the name (description)
@@ -47,11 +47,11 @@ refers to it exits.
 .PP
 If a process doesn't have a session keyring when it is accessed, then,
 under certain circumstances, the
-.BR user-session-keyring (7)
+.BR user\-session\-keyring (7)
 will be attached as the session keyring
 and under others a new session keyring will be created.
 (See
-.BR user-session-keyring (7)
+.BR user\-session\-keyring (7)
 for further details.)
 .SS Special operations
 The

diff --git a/man7/signal.7 b/man7/signal.7
index 14de1723ccace7e1673c247377098ecbf6ca053f..6973a238459a03ab082007e4c8fc3bed7d40cdee 100644 (file)
--- a/man7/signal.7
+++ b/man7/signal.7
@@ -816,7 +816,7 @@ Linux 2.4 and earlier:
 POSIX.1, except as noted.
 .SH NOTES
 For a discussion of async-signal-safe functions, see
-.BR signal-safety (7).
+.BR signal\-safety (7).
 .PP
 The
 .I /proc/[pid]/task/[tid]/status

diff --git a/man7/unicode.7 b/man7/unicode.7
index e972f8435699b112620ea8a779d04f01035fe83e..efb3897c56d229f70b99a6d98fd90eff90f2de4d 100644 (file)
--- a/man7/unicode.7
+++ b/man7/unicode.7
@@ -263,4 +263,4 @@ Bruno Haible: Unicode HOWTO.
 .BR locale (1),
 .BR setlocale (3),
 .BR charsets (7),
-.BR utf-8 (7)
+.BR utf\-8 (7)

diff --git a/man7/uri.7 b/man7/uri.7
index cadfad0c77f5c25ee60215987f2d5e64043798db..a978db71e2070e2feaf41e5f453b6c4269460cc3 100644 (file)
--- a/man7/uri.7
+++ b/man7/uri.7
@@ -531,7 +531,7 @@ the HTML 4.01 specification (section B.2) and
 IETF RFC\ 2718 (section 2.2.5) recommend the following approach:
 .IP 1. 4
 translate the character sequences into UTF-8 (IETF RFC\ 2279)\(emsee
-.BR utf-8 (7)\(emand
+.BR utf\-8 (7)\(emand
 then
 .IP 2.
 use the URI escaping mechanism, that is,

diff --git a/man7/user-keyring.7 b/man7/user-keyring.7
index 301c9a92da4caaa2bf41ebf1197ce2e9c9cd1d05..f13674eeeaa3cf3e08a41adbcab39047bf33758e 100644 (file)
--- a/man7/user-keyring.7
+++ b/man7/user-keyring.7
@@ -26,9 +26,9 @@ The user keyring is associated with the record that the kernel maintains
 for the UID.
 It comes into existence upon the first attempt to access either the
 user keyring, the
-.BR user-session-keyring (7),
+.BR user\-session\-keyring (7),
 or the
-.BR session-keyring (7).
+.BR session\-keyring (7).
 The keyring remains pinned in existence so long as there are processes
 running with that real UID or files opened by those processes remain open.
 (The keyring can also be pinned indefinitely by linking it
@@ -69,7 +69,7 @@ If it is necessary for a key associated with a user to exist beyond the UID
 record being garbage collected\(emfor example, for use by a
 .BR cron (8)
 script\(emthen the
-.BR persistent-keyring (7)
+.BR persistent\-keyring (7)
 should be used instead.
 .PP
 If a user keyring does not exist when it is accessed, it will be created.

diff --git a/man7/user-session-keyring.7 b/man7/user-session-keyring.7
index ec3fc9d620483b0a2715795dab3f3358310f590c..91664dd50297ac19e2c0fde5b1fa8ee4b701c0a0 100644 (file)
--- a/man7/user-session-keyring.7
+++ b/man7/user-session-keyring.7
@@ -26,9 +26,9 @@ The user session keyring is associated with the record that
 the kernel maintains for the UID.
 It comes into existence upon the first attempt to access either the
 user session keyring, the
-.BR user-keyring (7),
+.BR user\-keyring (7),
 or the
-.BR session-keyring (7).
+.BR session\-keyring (7).
 .\" Davis Howells: the user and user-session keyrings are managed as a pair.
 The keyring remains pinned in existence so long as there are processes
 running with that real UID or files opened by those processes remain open.
@@ -37,7 +37,7 @@ into another keyring.)
 .PP
 The user session keyring is created on demand when a thread requests it
 or when a thread asks for its
-.BR session-keyring (7)
+.BR session\-keyring (7)
 and that keyring doesn't exist.
 In the latter case, a user session keyring will be created and,
 if the session keyring wasn't to be created,
@@ -74,7 +74,7 @@ it will be created.
 Rather than relying on the user session keyring,
 it is strongly recommended\(emespecially if the process
 is running as root\(emthat a
-.BR session-keyring (7)
+.BR session\-keyring (7)
 be set explicitly, for example by
 .BR pam_keyinit (8).
 .SH NOTES
@@ -84,7 +84,7 @@ perhaps because it was created via a pathway that didn't involve PAM
 (e.g., perhaps it was a daemon started by
 .BR inetd (8)).
 In such a scenario, the user session keyring acts as a substitute for the
-.BR session-keyring (7).
+.BR session\-keyring (7).
 .SH SEE ALSO
 .ad l
 .nh