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 /man5/proc.5 | |
| 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 'man5/proc.5')
| -rw-r--r-- | man5/proc.5 | 56 |
1 files changed, 28 insertions, 28 deletions
diff --git a/man5/proc.5 b/man5/proc.5 index 6efdc51cbf..7d09da6bb0 100644 --- a/man5/proc.5 +++ b/man5/proc.5 @@ -245,12 +245,12 @@ things work as expected for the container "root" user. .IP The process's "dumpable" attribute may change for the following reasons: .RS -.IP \(bu 3 +.IP \[bu] 3 The attribute was explicitly set via the .BR prctl (2) .B PR_SET_DUMPABLE operation. -.IP \(bu +.IP \[bu] The attribute was reset to the value in the file .I /proc/sys/fs/suid_dumpable (described below), for the reasons described in @@ -1653,7 +1653,7 @@ with increases (+) or decreases (\-) for factors including: .\" See mm/oom_kill.c::oom_badness() after Linux 2.6.36 .\" commit a63d83f427fbce97a6cea0db2e64b0eb8435cd10 .RS -.IP \(bu 3 +.IP \[bu] 3 whether the process is privileged (\-). .\" More precisely, if it has CAP_SYS_ADMIN or (pre 2.6.36) CAP_SYS_RESOURCE .RE @@ -1661,16 +1661,16 @@ whether the process is privileged (\-). Before Linux 2.6.36 the following factors were also used in the calculation of oom_score: .RS -.IP \(bu 3 +.IP \[bu] 3 whether the process creates a lot of children using .BR fork (2) (+); -.IP \(bu +.IP \[bu] whether the process has been running a long time, or has used a lot of CPU time (\-); -.IP \(bu +.IP \[bu] whether the process has a low nice value (i.e., > 0) (+); and -.IP \(bu +.IP \[bu] whether the process is making direct hardware access (\-). .\" More precisely, if it has CAP_SYS_RAWIO .RE @@ -4316,16 +4316,16 @@ pseudo-file. This value is not reliable, for the following reasons: .\" See kernel commit 9c240d757658a3ae9968dd309e674c61f07c7f48 .RS -.IP \(bu 3 +.IP \[bu] 3 The CPU will not wait for I/O to complete; iowait is the time that a task is waiting for I/O to complete. When a CPU goes into idle state for outstanding task I/O, another task will be scheduled on this CPU. -.IP \(bu +.IP \[bu] On a multi-core CPU, the task waiting for I/O to complete is not running on any CPU, so the iowait of each CPU is difficult to calculate. -.IP \(bu +.IP \[bu] The value in this field may .I decrease in certain conditions. @@ -4484,19 +4484,19 @@ The file contains six numbers, .I want_pages (pages requested by system) and two dummy values. .RS -.IP \(bu 3 +.IP \[bu] 3 .I nr_dentry is the number of allocated dentries (dcache entries). This field is unused in Linux 2.2. -.IP \(bu +.IP \[bu] .I nr_unused is the number of unused dentries. -.IP \(bu +.IP \[bu] .I age_limit .\" looks like this is unused in Linux 2.2 to Linux 2.6 is the age in seconds after which dcache entries can be reclaimed when memory is short. -.IP \(bu +.IP \[bu] .I want_pages .\" looks like this is unused in Linux 2.2 to Linux 2.6 is nonzero when the kernel has called shrink_dcache_pages() and the @@ -4725,28 +4725,28 @@ When the value in this file is 1, a hard link can be created to a target file only if one of the following conditions is true: .RS -.IP \(bu 3 +.IP \[bu] 3 The calling process has the .B CAP_FOWNER capability in its user namespace and the file UID has a mapping in the namespace. -.IP \(bu +.IP \[bu] The filesystem UID of the process creating the link matches the owner (UID) of the target file (as described in .BR credentials (7), a process's filesystem UID is normally the same as its effective UID). -.IP \(bu +.IP \[bu] All of the following conditions are true: .RS 4 -.IP \(bu 3 +.IP \[bu] 3 the target is a regular file; -.IP \(bu +.IP \[bu] the target file does not have its set-user-ID mode bit enabled; -.IP \(bu +.IP \[bu] the target file does not have both its set-group-ID and group-executable mode bits enabled; and -.IP \(bu +.IP \[bu] the caller has permission to read and write the target file (either via the file's permissions mask or because it has suitable capabilities). @@ -4801,15 +4801,15 @@ no restrictions are placed on following symbolic links When the value in this file is 1, symbolic links are followed only in the following circumstances: .RS -.IP \(bu 3 +.IP \[bu] 3 the filesystem UID of the process following the link matches the owner (UID) of the symbolic link (as described in .BR credentials (7), a process's filesystem UID is normally the same as its effective UID); -.IP \(bu +.IP \[bu] the link is not in a sticky world-writable directory; or -.IP \(bu +.IP \[bu] the symbolic link and its parent directory have the same owner (UID) .RE .IP @@ -5890,18 +5890,18 @@ CommitLimit = (total_RAM \- total_huge_TLB) * .IP where: .RS -.IP \(bu 3 +.IP \[bu] 3 .I total_RAM is the total amount of RAM on the system; -.IP \(bu +.IP \[bu] .I total_huge_TLB is the amount of memory set aside for huge pages; -.IP \(bu +.IP \[bu] .I overcommit_ratio is the value in .IR /proc/sys/vm/overcommit_ratio ; and -.IP \(bu +.IP \[bu] .I total_swap is the amount of swap space. .RE |