From: Phillip Susi Date: Sat, 8 Feb 2014 18:22:10 +0000 (-0500) Subject: renice: correct max priority in renice man page X-Git-Tag: v2.25-rc1~607 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=e8f348035488124fe7dd36110813765bcc26d76d;p=thirdparty%2Futil-linux.git 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 Signed-off-by: Karel Zak --- diff --git a/sys-utils/renice.1 b/sys-utils/renice.1 index 538687e341..8a332e140d 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