aboutsummaryrefslogtreecommitdiffstats
path: root/man7/user-keyring.7
diff options
context:
space:
mode:
authorMichael Kerrisk <mtk.manpages@gmail.com>2020-07-06 14:28:51 +0200
committerMichael Kerrisk <mtk.manpages@gmail.com>2020-07-06 14:28:51 +0200
commit28a4c58cc211900943f48d65fd42b313ce54e5a6 (patch)
tree153dcbcc3fb2a17ae9437a157399838e350436fb /man7/user-keyring.7
parent168aac07bd0a48f6d99ca75354e8ef77ae26db93 (diff)
downloadman-pages-28a4c58cc211900943f48d65fd42b313ce54e5a6.tar.gz
intro.1, localedef.1, memusage.1, memusagestat.1, bpf.2, execve.2, fork.2, keyctl.2, request_key.2, sigaction.2, signal.2, socket.2, dlopen.3, getauxval.3, gnu_get_libc_version.3, pthread_atfork.3, sem_post.3, setjmp.3, strftime.3, veth.4, locale.5, nscd.conf.5, resolv.conf.5, address_families.7, armscii-8.7, ascii.7, capabilities.7, cgroups.7, charsets.7, cp1251.7, cp1252.7, iso_8859-1.7, iso_8859-10.7, iso_8859-11.7, iso_8859-13.7, iso_8859-14.7, iso_8859-15.7, iso_8859-16.7, iso_8859-2.7, iso_8859-3.7, iso_8859-4.7, iso_8859-5.7, iso_8859-6.7, iso_8859-7.7, iso_8859-8.7, iso_8859-9.7, keyrings.7, koi8-r.7, koi8-u.7, libc.7, locale.7, man.7, network_namespaces.7, persistent-keyring.7, session-keyring.7, signal.7, unicode.7, uri.7, user-keyring.7, user-session-keyring.7: ffix: replace - with real\-
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
Diffstat (limited to 'man7/user-keyring.7')
-rw-r--r--man7/user-keyring.76
1 files changed, 3 insertions, 3 deletions
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.