console_codes.4: Document that \e[1;n] and \e[2;n] support 16 colors

[thirdparty/man-pages.git] / man7 / user-session-keyring.7

diff --git a/man7/user-session-keyring.7 b/man7/user-session-keyring.7
index 42174a800e2c0f8f709ee2db2b289c48f175be92..5824a0f92d74f3fd29bcf8e9408f3f490ca29799 100644 (file)
--- a/man7/user-session-keyring.7
+++ b/man7/user-session-keyring.7
@@ -4,19 +4,24 @@
 .\"
 .\" %%%LICENSE_START(GPLv2+_SW_ONEPARA)
 .\" This program is free software; you can redistribute it and/or
-.\" modify it under the terms of the GNU General Public Licence
+.\" modify it under the terms of the GNU General Public License
 .\" as published by the Free Software Foundation; either version
-.\" 2 of the Licence, or (at your option) any later version.
+.\" 2 of the License, or (at your option) any later version.
 .\" %%%LICENSE_END
 .\"
-.TH "USER-SESSION-KEYRING" 7 2016-11-01 Linux "Linux Programmer's Manual"
+.TH "USER-SESSION-KEYRING" 7 2017-03-13 Linux "Linux Programmer's Manual"
 .SH NAME
 user-session-keyring \- per-user default session keyring
 .SH DESCRIPTION
 The user session keyring is a keyring used to anchor keys on behalf of a user.
 Each UID the kernel deals with has its own user session keyring that
 is shared by all processes with that UID.
-
+The user session keyring has a name (description) of the form
+.I _uid_ses.<UID>
+where
+.I <UID>
+is the user ID of the corresponding user.
+.PP
 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
@@ -29,7 +34,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
 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)
@@ -37,22 +42,22 @@ 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,
 the user session keyring will be set as the process's actual session keyring.
-
+.PP
 The user session keyring is searched by
 .BR request_key (2)
 if the actual session keyring does not exist and is ignored otherwise.
-
+.PP
 A special serial number value,
 .BR KEY_SPEC_USER_SESSION_KEYRING ,
 is defined
 that can be used in lieu of the actual serial number of
 the calling process's user session keyring.
-
+.PP
 From the
 .BR keyctl (1)
 utility, '\fB@us\fP' can be used instead of a numeric key ID in
 much the same way.
-
+.PP
 User session keyrings are independent of
 .BR clone (2),
 .BR fork (2),
@@ -62,10 +67,10 @@ and
 .BR _exit (2)
 excepting that the keyring is destroyed when the UID record is destroyed
 when the last process pinning it exits.
-
+.PP
 If a user session keyring does not exist when it is accessed,
 it will be created.
-
+.PP
 Rather than relying on the user session keyring,
 it is strongly recommended\(emespecially if the process
 is running as root\(emthat a