diff options
| author | Phillip Susi <psusi@ubuntu.com> | 2014-02-08 13:22:10 -0500 |
|---|---|---|
| committer | Karel Zak <kzak@redhat.com> | 2014-04-23 10:54:31 +0200 |
| commit | 1a2fc7b4b32b52117e09dbd04459bc57cf892956 (patch) | |
| tree | aadfbff772d06daee236a9d3c73affe08f9a66e7 | |
| parent | 8a44a9d8dc78c81995ded6864e2e405ade6888e0 (diff) | |
| download | util-linux-1a2fc7b4b32b52117e09dbd04459bc57cf892956.tar.gz | |
renice: correct max priority in renice man page
The man page stated that the PRIO_MAX is 20. While this
is correct, the header definition is wrong and the max
value is actually 19.
[kzak@redhat.com: - remove PRIO_MAX from man page, kernel syscalls
use hardcoded numbers for the priority limits]
Signed-off-by: Phillip Susi <psusi@ubuntu.com>
Signed-off-by: Karel Zak <kzak@redhat.com>
| -rw-r--r-- | sys-utils/renice.1 | 10 |
1 files changed, 3 insertions, 7 deletions
diff --git a/sys-utils/renice.1 b/sys-utils/renice.1 index 538687e34..8a332e140 100644 --- a/sys-utils/renice.1 +++ b/sys-utils/renice.1 @@ -85,15 +85,11 @@ PIDs 987 and 32, plus all processes owned by the users daemon and root: .SH NOTES Users other than the superuser may only alter the priority of processes they own, and can only monotonically increase their ``nice value'' (for security -reasons) within the range 0 to -.BR PRIO_MAX \ (20), +reasons) within the range 0 to 19, unless a nice resource limit is set (Linux 2.6.12 and higher). The superuser may alter the priority of any process and set the priority to any -value in the range -.BR PRIO_MIN \ (\-20) -to -.BR PRIO_MAX . -Useful priorities are: 20 (the affected processes will run only when nothing +value in the range \-20 to 19. +Useful priorities are: 19 (the affected processes will run only when nothing else in the system wants to), 0 (the ``base'' scheduling priority), anything negative (to make things go very fast). .SH FILES |