diff options
Diffstat (limited to 'man7')
37 files changed, 103 insertions, 103 deletions
diff --git a/man7/address_families.7 b/man7/address_families.7 index feaadf0891..c68324f7e2 100644 --- 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 9ee2341a02..94c51e3680 100644 --- 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 8780c48f96..11b311f9d4 100644 --- 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 d7c50f716b..fd841b4f16 100644 --- 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 5d060c2ada..59598016ab 100644 --- 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 95085e4844..439ea73437 100644 --- 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 4d48fd138b..382de42c85 100644 --- 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 013acc53ff..07ac84bf5d 100644 --- 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 5607545b99..202768231f 100644 --- 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 f299fb43c0..82c8eeda5f 100644 --- 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 2147ff3a71..073ddc6577 100644 --- 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 030de5414e..06de48839a 100644 --- 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 3a0d2cdee8..592bd0838e 100644 --- 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 1bf9aa7f2b..5e71a41aae 100644 --- 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 991fc13b1d..8d9b5a2595 100644 --- 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 2b3863bba1..095f0612d0 100644 --- 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 fe7d60d104..5f2605852f 100644 --- 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 ec3d5d2e5e..6eefaef939 100644 --- 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 4a4933613b..7e3c8cec10 100644 --- 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 8f52e7b61f..5e1608a2e3 100644 --- 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 3ede304553..f595708880 100644 --- 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 c1d294ea04..b7e1c5f7b5 100644 --- 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 78184d6210..b97efc29cf 100644 --- 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 e943cd4b86..0e0bd0a951 100644 --- 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 140521eb34..7ee9e2927d 100644 --- 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 55e8766c6d..0c56e949f3 100644 --- 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 66b06a2671..2809a97cee 100644 --- 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 d8da47c31e..ca3f05725d 100644 --- 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 43bd0b9622..559d40db65 100644 --- 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 e227ece504..aa1b045895 100644 --- 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 46e92231e3..3367ec153f 100644 --- 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 3b9a008708..0b886be5e7 100644 --- 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 14de1723cc..6973a23845 100644 --- 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 e972f84356..efb3897c56 100644 --- 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 cadfad0c77..a978db71e2 100644 --- 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 301c9a92da..f13674eeea 100644 --- 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 ec3fc9d620..91664dd502 100644 --- 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 |