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. Signed-off-by: Phillip Susi <psusi@xxxxxxxxxx> --- sys-utils/renice.1 | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/sys-utils/renice.1 b/sys-utils/renice.1 index 538687e..9cb50b8 100644 --- a/sys-utils/renice.1 +++ b/sys-utils/renice.1 @@ -86,14 +86,14 @@ PIDs 987 and 32, plus all processes owned by the users daemon and root: 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), +.BR PRIO_MAX \ (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 +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 -- 1.8.3.2 -- To unsubscribe from this list: send the line "unsubscribe util-linux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
