diff options
| author | Alejandro Colomar <alx@kernel.org> | 2023-02-05 23:14:38 +0100 |
|---|---|---|
| committer | Alejandro Colomar <alx@kernel.org> | 2023-02-05 23:14:42 +0100 |
| commit | cdede5cdd1b0ba75135d3b32d96354026e96f866 (patch) | |
| tree | f21d7604d25b2de607ef5471e5e180094231e046 /man7/namespaces.7 | |
| parent | f29fc8dcf0da15a596a7cdc7e5a0b2932100b522 (diff) | |
| download | man-pages-cdede5cdd1b0ba75135d3b32d96354026e96f866.tar.gz | |
Many pages: Use \[bu] instead of \(bu
Signed-off-by: Alejandro Colomar <alx@kernel.org>
Diffstat (limited to 'man7/namespaces.7')
| -rw-r--r-- | man7/namespaces.7 | 36 |
1 files changed, 18 insertions, 18 deletions
diff --git a/man7/namespaces.7 b/man7/namespaces.7 index e82bb4d154..97d9c1bce1 100644 --- a/man7/namespaces.7 +++ b/man7/namespaces.7 @@ -311,48 +311,48 @@ The value in this file defines a per-user limit on the number of uts namespaces that may be created in the user namespace. .PP Note the following details about these files: -.IP \(bu 3 +.IP \[bu] 3 The values in these files are modifiable by privileged processes. -.IP \(bu +.IP \[bu] The values exposed by these files are the limits for the user namespace in which the opening process resides. -.IP \(bu +.IP \[bu] The limits are per-user. Each user in the same user namespace can create namespaces up to the defined limit. -.IP \(bu +.IP \[bu] The limits apply to all users, including UID 0. -.IP \(bu +.IP \[bu] These limits apply in addition to any other per-namespace limits (such as those for PID and user namespaces) that may be enforced. -.IP \(bu +.IP \[bu] Upon encountering these limits, .BR clone (2) and .BR unshare (2) fail with the error .BR ENOSPC . -.IP \(bu +.IP \[bu] For the initial user namespace, the default value in each of these files is half the limit on the number of threads that may be created .RI ( /proc/sys/kernel/threads\-max ). In all descendant user namespaces, the default value in each file is .BR MAXINT . -.IP \(bu +.IP \[bu] When a namespace is created, the object is also accounted against ancestor namespaces. More precisely: .RS -.IP \(bu 3 +.IP \[bu] 3 Each user namespace has a creator UID. -.IP \(bu +.IP \[bu] When a namespace is created, it is accounted against the creator UIDs in each of the ancestor user namespaces, and the kernel ensures that the corresponding namespace limit for the creator UID in the ancestor namespace is not exceeded. -.IP \(bu +.IP \[bu] The aforementioned point ensures that creating a new user namespace cannot be used as a means to escape the limits in force in the current user namespace. @@ -365,32 +365,32 @@ the namespace terminates or leaves the namespace. However, there are a number of other factors that may pin a namespace into existence even though it has no member processes. These factors include the following: -.IP \(bu 3 +.IP \[bu] 3 An open file descriptor or a bind mount exists for the corresponding .IR /proc/ pid /ns/* file. -.IP \(bu +.IP \[bu] The namespace is hierarchical (i.e., a PID or user namespace), and has a child namespace. -.IP \(bu +.IP \[bu] It is a user namespace that owns one or more nonuser namespaces. -.IP \(bu +.IP \[bu] It is a PID namespace, and there is a process that refers to the namespace via a .IR /proc/ pid /ns/pid_for_children symbolic link. -.IP \(bu +.IP \[bu] It is a time namespace, and there is a process that refers to the namespace via a .IR /proc/ pid /ns/time_for_children symbolic link. -.IP \(bu +.IP \[bu] It is an IPC namespace, and a corresponding mount of an .I mqueue filesystem (see .BR mq_overview (7)) refers to this namespace. -.IP \(bu +.IP \[bu] It is a PID namespace, and a corresponding mount of a .BR proc (5) filesystem refers to this namespace. |