aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorAlejandro Colomar <alx@kernel.org>2024-02-25 16:45:30 +0100
committerAlejandro Colomar <alx@kernel.org>2024-02-25 17:24:41 +0100
commitc40c1a54b856d30bca4b3e7b2fc61e7fcb828557 (patch)
tree34d30be13aa8b822624043e62256d10b896cf49d
parent21259e57ac8406b9ccc7107229895d8e621a1a33 (diff)
downloadman-pages-c40c1a54b856d30bca4b3e7b2fc61e7fcb828557.tar.gz
man*/: srcfix
Found with: $ grep -rn '"""' man* \ | grep -v '"""""""""""' \ | sed 's/:.*//' \ | sort \ | uniq; man2/add_key.2 man2/getrlimit.2 man2/keyctl.2 man2/pivot_root.2 man2/request_key.2 man3/isalpha.3 man3/setlocale.3 man3/toupper.3 man7/capabilities.7 man7/cgroups.7 man7/keyrings.7 man7/locale.7 man7/user_namespaces.7 Signed-off-by: Alejandro Colomar <alx@kernel.org>
-rw-r--r--man2/add_key.218
-rw-r--r--man2/getrlimit.22
-rw-r--r--man2/keyctl.24
-rw-r--r--man2/pivot_root.26
-rw-r--r--man2/request_key.26
-rw-r--r--man3/isalpha.34
-rw-r--r--man3/setlocale.38
-rw-r--r--man3/toupper.32
-rw-r--r--man7/capabilities.72
-rw-r--r--man7/cgroups.736
-rw-r--r--man7/keyrings.726
-rw-r--r--man7/locale.72
-rw-r--r--man7/user_namespaces.72
13 files changed, 59 insertions, 59 deletions
diff --git a/man2/add_key.2 b/man2/add_key.2
index 3a706c8295..2b017f6803 100644
--- a/man2/add_key.2
+++ b/man2/add_key.2
@@ -96,7 +96,7 @@ argument to
.BR add_key ()
are the following:
.TP
-.I """keyring"""
+.I \[dq]keyring\[dq]
Keyrings are special key types that may contain links to sequences of other
keys of any type.
If this interface is used to create a keyring, then
@@ -105,17 +105,17 @@ should be NULL and
.I plen
should be zero.
.TP
-.I """user"""
+.I \[dq]user\[dq]
This is a general purpose key type whose payload may be read and updated
by user-space applications.
The key is kept entirely within kernel memory.
The payload for keys of this type is a blob of arbitrary data
of up to 32,767 bytes.
.TP
-.IR """logon""" " (since Linux 3.3)"
+.IR \[dq]logon\[dq] " (since Linux 3.3)"
.\" commit 9f6ed2ca257fa8650b876377833e6f14e272848b
This key type is essentially the same as
-.IR """user""" ,
+.IR \[dq]user\[dq] ,
but it does not permit the key to read.
This is suitable for storing payloads
that you do not want to be readable from user space.
@@ -127,10 +127,10 @@ by checking to ensure that the
.I description
contains a ':' that is preceded by other characters.
.TP
-.IR """big_key""" " (since Linux 3.13)"
+.IR \[dq]big_key\[dq] " (since Linux 3.13)"
.\" commit ab3c3587f8cda9083209a61dbe3a4407d3cada10
This key type is similar to
-.IR """user""" ,
+.IR \[dq]user\[dq] ,
but may hold a payload of up to 1\ MiB.
If the key payload is large enough,
then it may be stored encrypted in tmpfs
@@ -175,11 +175,11 @@ The payload data was invalid.
.B EINVAL
.I type
was
-.I """logon"""
+.I \[dq]logon\[dq]
and the
.I description
was not qualified with a prefix string of the form
-.IR """service:""" .
+.IR \[dq]service:\[dq] .
.TP
.B EKEYEXPIRED
The keyring has expired.
@@ -202,7 +202,7 @@ Key types that begin with a period are reserved to the implementation.
.B EPERM
.I type
was
-.I """keyring"""
+.I \[dq]keyring\[dq]
and the
.I description
started with a period (\[aq].\[aq]).
diff --git a/man2/getrlimit.2 b/man2/getrlimit.2
index 68f880d5a3..b1254f6188 100644
--- a/man2/getrlimit.2
+++ b/man2/getrlimit.2
@@ -717,7 +717,7 @@ Linux doesn't return an error when an attempt to set
.B RLIMIT_CPU
has failed, for compatibility reasons.
.\"
-.SS Representation of """large""" resource limit values on 32-bit platforms
+.SS Representation of \[dq]large\[dq] resource limit values on 32-bit platforms
The glibc
.BR getrlimit ()
and
diff --git a/man2/keyctl.2 b/man2/keyctl.2
index 7d4324f85a..a2a4ab047f 100644
--- a/man2/keyctl.2
+++ b/man2/keyctl.2
@@ -1415,7 +1415,7 @@ The
.I arg2
argument is a pointer to a set of parameters containing
serial numbers for three
-.I """user"""
+.I \[dq]user\[dq]
keys used in the Diffie-Hellman calculation,
packaged in a structure of the following form:
.IP
@@ -1897,7 +1897,7 @@ was
.B KEYCTL_READ
and the key type does not support reading
(e.g., the type is
-.IR """login""" ).
+.IR \[dq]login\[dq] ).
.TP
.B EOPNOTSUPP
.I operation
diff --git a/man2/pivot_root.2 b/man2/pivot_root.2
index 832637dc5f..9cb5d9b258 100644
--- a/man2/pivot_root.2
+++ b/man2/pivot_root.2
@@ -66,7 +66,7 @@ must yield the same directory as \fInew_root\fP.
.IP \[bu]
.I new_root
must be a path to a mount point, but can't be
-.IR """/""" .
+.IR \[dq]/\[dq] .
A path that is not already a mount point can be converted into one by
bind mounting the path onto itself.
.IP \[bu]
@@ -115,7 +115,7 @@ is on the current root mount.
(This error covers the pathological case where
.I new_root
is
-.IR """/""" .)
+.IR \[dq]/\[dq] .)
.TP
.B EINVAL
.I new_root
@@ -227,7 +227,7 @@ working directory refer to the new root mount point
During the subsequent
.BR umount ()
call, resolution of
-.I """."""
+.I \[dq].\[dq]
starts with
.I new_root
and then moves up the list of mounts stacked at
diff --git a/man2/request_key.2 b/man2/request_key.2
index 89815c4ed7..53c47e450b 100644
--- a/man2/request_key.2
+++ b/man2/request_key.2
@@ -227,7 +227,7 @@ The authorization key is constructed as follows:
.RS
.IP \[bu] 3
The key type is
-.IR """.request_key_auth""" .
+.IR \[dq].request_key_auth\[dq] .
.IP \[bu]
The key's UID and GID are the same as the corresponding filesystem IDs
of the requesting process.
@@ -263,10 +263,10 @@ This program is supplied with the following command-line arguments:
.RS
.IP [0] 5
The string
-.IR """/sbin/request\-key""" .
+.IR \[dq]/sbin/request\-key\[dq] .
.IP [1]
The string
-.I """create"""
+.I \[dq]create\[dq]
(indicating that a key is to be created).
.IP [2]
The ID of the key that is to be instantiated.
diff --git a/man3/isalpha.3 b/man3/isalpha.3
index d1fbd17b66..05d3737808 100644
--- a/man3/isalpha.3
+++ b/man3/isalpha.3
@@ -170,9 +170,9 @@ alphanumeric character.
.BR isspace ()
checks for white-space characters.
In the
-.B """C"""
+.B \[dq]C\[dq]
and
-.B """POSIX"""
+.B \[dq]POSIX\[dq]
locales, these are: space, form-feed
.RB ( \[aq]\ef\[aq] ),
newline
diff --git a/man3/setlocale.3 b/man3/setlocale.3
index 3be5101154..3ec86d5a5a 100644
--- a/man3/setlocale.3
+++ b/man3/setlocale.3
@@ -92,7 +92,7 @@ Such a string is either a well-known constant like "C" or "da_DK"
If
.I locale
is an empty string,
-.BR """""" ,
+.BR \[dq]\[dq] ,
each part of the locale that should be modified is set according to the
environment variables.
The details are implementation-dependent.
@@ -112,9 +112,9 @@ is unchanged, and
returns NULL.
.P
The locale
-.B """C"""
+.B \[dq]C\[dq]
or
-.B """POSIX"""
+.B \[dq]POSIX\[dq]
is a portable locale;
it exists on all conforming systems.
.P
@@ -138,7 +138,7 @@ If
is NULL, the current locale is only queried, not modified.
.P
On startup of the main program, the portable
-.B """C"""
+.B \[dq]C\[dq]
locale is selected as default.
A program may be made portable to all locales by calling:
.P
diff --git a/man3/toupper.3 b/man3/toupper.3
index a7367f6fab..98a111c812 100644
--- a/man3/toupper.3
+++ b/man3/toupper.3
@@ -166,7 +166,7 @@ yielding a value that is outside the range of
The details of what constitutes an uppercase or lowercase letter depend
on the locale.
For example, the default
-.B """C"""
+.B \[dq]C\[dq]
locale does not know about umlauts, so no conversion is done for them.
.P
In some non-English locales, there are lowercase letters with no
diff --git a/man7/capabilities.7 b/man7/capabilities.7
index ab93799787..b86ef7af0e 100644
--- a/man7/capabilities.7
+++ b/man7/capabilities.7
@@ -1683,7 +1683,7 @@ prctl(PR_SET_SECUREBITS,
.in
.\"
.\"
-.SS Per-user-namespace """set-user-ID-root""" programs
+.SS Per-user-namespace \[dq]set-user-ID-root\[dq] programs
A set-user-ID program whose UID matches the UID that
created a user namespace will confer capabilities
in the process's permitted and effective sets
diff --git a/man7/cgroups.7 b/man7/cgroups.7
index d4e559302d..ca10cf859a 100644
--- a/man7/cgroups.7
+++ b/man7/cgroups.7
@@ -805,7 +805,7 @@ then the corresponding controller-interface files (e.g.,
are automatically created in the children of that cgroup
and can be used to exert resource control in the child cgroups.
.\"
-.SS Cgroups v2 """no internal processes""" rule
+.SS Cgroups v2 \[dq]no internal processes\[dq] rule
Cgroups v2 enforces a so-called "no internal processes" rule.
Roughly speaking, this rule means that,
with the exception of the root cgroup, processes may reside
@@ -974,10 +974,10 @@ fails with the error
.BR EAGAIN ).
.IP
Writing the string
-.I """max"""
+.I \[dq]max\[dq]
to this file means that no limit is imposed.
The default value in this file is
-.IR """max""" .
+.IR \[dq]max\[dq] .
.TP
.IR cgroup.max.descendants " (since Linux 4.14)"
.\" commit 1a926e0bbab83bae8207d05a533173425e0496d1
@@ -989,10 +989,10 @@ fails with the error
.BR EAGAIN ).
.IP
Writing the string
-.I """max"""
+.I \[dq]max\[dq]
to this file means that no limit is imposed.
The default value in this file is
-.IR """max""" .
+.IR \[dq]max\[dq] .
.\"
.SH CGROUPS DELEGATION: DELEGATING A HIERARCHY TO A LESS PRIVILEGED USER
In the context of cgroups,
@@ -1327,7 +1327,7 @@ The only thing that can be done with this cgroup (other than deleting it)
is to convert it to a
.I threaded
cgroup by writing the string
-.I """threaded"""
+.I \[dq]threaded\[dq]
to the
.I cgroup.type
file.
@@ -1369,7 +1369,7 @@ There are two pathways that lead to the creation of a threaded subtree.
The first pathway proceeds as follows:
.IP (1) 5
We write the string
-.I """threaded"""
+.I \[dq]threaded\[dq]
to the
.I cgroup.type
file of a cgroup
@@ -1406,7 +1406,7 @@ will also have the type
.RE
.IP (2)
We write the string
-.I """threaded"""
+.I \[dq]threaded\[dq]
to each of the
.I domain invalid
cgroups under
@@ -1418,7 +1418,7 @@ now have the type
.I threaded
and the threaded subtree is now fully usable.
The requirement to write
-.I """threaded"""
+.I \[dq]threaded\[dq]
to each of these cgroups is somewhat cumbersome,
but allows for possible future extensions to the thread-mode model.
.P
@@ -1449,7 +1449,7 @@ are converted to type
.RE
.IP (2)
As before, we make the threaded subtree usable by writing the string
-.I """threaded"""
+.I \[dq]threaded\[dq]
to each of the
.I domain invalid
cgroups under
@@ -1553,7 +1553,7 @@ A number of rules apply when writing to the
file:
.IP \[bu] 3
Only the string
-.I """threaded"""
+.I \[dq]threaded\[dq]
may be written.
In other words, the only explicit transition that is possible is to convert a
.I domain
@@ -1561,7 +1561,7 @@ cgroup to type
.IR threaded .
.IP \[bu]
The effect of writing
-.I """threaded"""
+.I \[dq]threaded\[dq]
depends on the current value in
.IR cgroup.type ,
as follows:
@@ -1607,20 +1607,20 @@ No domain controllers may be enabled in
file.
.P
If any of the above constraints is violated, then an attempt to write
-.I """threaded"""
+.I \[dq]threaded\[dq]
to a
.I cgroup.type
file fails with the error
.BR ENOTSUP .
.\"
-.SS The """domain threaded""" cgroup type
+.SS The \[dq]domain threaded\[dq] cgroup type
According to the pathways described above,
the type of a cgroup can change to
.I domain threaded
in either of the following cases:
.IP \[bu] 3
The string
-.I """threaded"""
+.I \[dq]threaded\[dq]
is written to a child cgroup.
.IP \[bu]
A threaded controller is enabled inside the cgroup and
@@ -1666,7 +1666,7 @@ and
.I threaded
cgroups.
If the string
-.I """threaded"""
+.I \[dq]threaded\[dq]
is written to the
.I cgroup.type
file of one of the children of the root cgroup, then
@@ -1690,7 +1690,7 @@ allow a threaded cgroup that employs the
controller to be placed as high as possible in the hierarchy,
so as to minimize the (small) cost of traversing the cgroup hierarchy.
.\"
-.SS The cgroups v2 """cpu""" controller and realtime threads
+.SS The cgroups v2 \[dq]cpu\[dq] controller and realtime threads
As at Linux 4.19, the cgroups v2
.I cpu
controller does not support control of realtime threads
@@ -1708,7 +1708,7 @@ if all realtime threads are in the root cgroup.
(If there are realtime threads in nonroot cgroups, then a
.BR write (2)
of the string
-.I """+cpu"""
+.I \[dq]+cpu\[dq]
to the
.I cgroup.subtree_control
file fails with the error
diff --git a/man7/keyrings.7 b/man7/keyrings.7
index 7d9c4a0cfa..96683f545c 100644
--- a/man7/keyrings.7
+++ b/man7/keyrings.7
@@ -98,7 +98,7 @@ the key is scheduled for garbage collection.
.SS Key types
The kernel provides several basic types of key:
.TP
-.I """keyring"""
+.I \[dq]keyring\[dq]
.\" Note that keyrings use different fields in struct key in order to store
.\" their data - index_key instead of type/description and name_link/keys
.\" instead of payload.
@@ -111,7 +111,7 @@ being garbage collected because nothing refers to them.
Keyrings with descriptions (names)
that begin with a period (\[aq].\[aq]) are reserved to the implementation.
.TP
-.I """user"""
+.I \[dq]user\[dq]
This is a general-purpose key type.
The key is kept entirely within kernel memory.
The payload may be read and updated by user-space applications.
@@ -123,12 +123,12 @@ The description may be any valid string, though it is preferred that it
start with a colon-delimited prefix representing the service
to which the key is of interest
(for instance
-.IR """afs:mykey""" ).
+.IR \[dq]afs:mykey\[dq] ).
.TP
-.IR """logon""" " (since Linux 3.3)"
+.IR \[dq]logon\[dq] " (since Linux 3.3)"
.\" commit 9f6ed2ca257fa8650b876377833e6f14e272848b
This key type is essentially the same as
-.IR """user""" ,
+.IR \[dq]user\[dq] ,
but it does not provide reading (i.e., the
.BR keyctl (2)
.B KEYCTL_READ
@@ -138,19 +138,19 @@ This is suitable for storing username-password pairs
that should not be readable from user space.
.IP
The description of a
-.I """logon"""
+.I \[dq]logon\[dq]
key
.I must
start with a non-empty colon-delimited prefix whose purpose
is to identify the service to which the key belongs.
(Note that this differs from keys of the
-.I """user"""
+.I \[dq]user\[dq]
type, where the inclusion of a prefix is recommended but is not enforced.)
.TP
-.IR """big_key""" " (since Linux 3.13)"
+.IR \[dq]big_key\[dq] " (since Linux 3.13)"
.\" commit ab3c3587f8cda9083209a61dbe3a4407d3cada10
This key type is similar to the
-.I """user"""
+.I \[dq]user\[dq]
key type, but it may hold a payload of up to 1\ MiB in size.
This key type is useful for purposes such as holding Kerberos ticket caches.
.IP
@@ -685,16 +685,16 @@ field provides some further information about the key.
The information that appears here depends on the key type, as follows:
.RS
.TP
-.IR """user""" " and " """logon"""
+.IR \[dq]user\[dq] " and " \[dq]logon\[dq]
The size in bytes of the key payload (expressed in decimal).
.TP
-.I """keyring"""
+.I \[dq]keyring\[dq]
The number of keys linked to the keyring,
or the string
.I empty
if there are no keys linked to the keyring.
.TP
-.I """big_key"""
+.I \[dq]big_key\[dq]
The payload size in bytes, followed either by the string
.IR [file] ,
if the key payload exceeds the threshold that means that the
@@ -707,7 +707,7 @@ indicating that the key is small enough to reside in kernel memory.
.RE
.IP
For the
-.I """.request_key_auth"""
+.I \[dq].request_key_auth\[dq]
key type
(authorization key; see
.BR request_key (2)),
diff --git a/man7/locale.7 b/man7/locale.7
index cfd79b259b..5a418ae13a 100644
--- a/man7/locale.7
+++ b/man7/locale.7
@@ -131,7 +131,7 @@ functions also obey the environment variable
.B LANGUAGE
(containing a colon-separated list of locales)
if the category is set to a valid locale other than
-.BR """C""" .
+.BR \[dq]C\[dq] .
This category also affects the behavior of
.BR catopen (3).
.TP
diff --git a/man7/user_namespaces.7 b/man7/user_namespaces.7
index 290771af2a..ddeb669c30 100644
--- a/man7/user_namespaces.7
+++ b/man7/user_namespaces.7
@@ -289,7 +289,7 @@ allows (since Linux 4.6)
that process to the mount the cgroup version 2 filesystem and
cgroup version 1 named hierarchies
(i.e., cgroup filesystems mounted with the
-.I """none,name="""
+.I \[dq]none,name=\[dq]
option).
.P
Holding