SCCS-vsn: usr.bin/renice/renice.8 6.2
.\" All rights reserved. The Berkeley software License Agreement
.\" specifies the terms and conditions for redistribution.
.\"
.\" All rights reserved. The Berkeley software License Agreement
.\" specifies the terms and conditions for redistribution.
.\"
-.\" @(#)renice.8 6.1 (Berkeley) %G%
+.\" @(#)renice.8 6.2 (Berkeley) %G%
.\"
.TH RENICE 8 ""
.UC 4
.\"
.TH RENICE 8 ""
.UC 4
Users other than the super-user may only alter the priority of
processes they own,
and can only monotonically increase their ``nice value''
Users other than the super-user may only alter the priority of
processes they own,
and can only monotonically increase their ``nice value''
-within the range 0 to PRIO_MIN (20).
+within the range 0 to PRIO_MAX (20).
(This prevents overriding administrative fiats.)
The super-user
may alter the priority of any process
(This prevents overriding administrative fiats.)
The super-user
may alter the priority of any process
-and set the priority to any value in the range PRIO_MAX (\-20)
-to PRIO_MIN.
+and set the priority to any value in the range PRIO_MIN (\-20)
+to PRIO_MAX.
-19 (the affected processes will run only when nothing else
+20 (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).
in the system wants to),
0 (the ``base'' scheduling priority),
anything negative (to make things go very fast).
.SH SEE ALSO
getpriority(2), setpriority(2)
.SH BUGS
.SH SEE ALSO
getpriority(2), setpriority(2)
.SH BUGS
-If you make the priority very negative,
-then the process cannot be interrupted.
-To regain control you make the priority greater than zero.
Non super-users can not increase scheduling priorities of their own processes,
even if they were the ones that decreased the priorities in the first place.
Non super-users can not increase scheduling priorities of their own processes,
even if they were the ones that decreased the priorities in the first place.