renice - alter priority of running processes
renice priority [[-p] pid ...] [[-g] pgrp ...] [[-u] user
renice alters the scheduling priority (an integer) of one or
processes. The following who parameters (pid, pgrp and user) are interpreted
as process IDs, process group IDs, or user names.
process group causes all processes in the process group to
scheduling priority altered. reniceing a user causes all
by the user to have their scheduling priority altered. By
processes to be affected are specified by their process IDs.
The options are as follows:
-g Force who parameters to be interpreted as process
-u Force the who parameters to be interpreted as user
-p Resets the who interpretation to be (the default)
# renice +1 987 -u daemon root -p 32
would change the priority of process IDs 987 and 32, and all
owned by users daemon and root.
Users other than the superuser may only alter the priority
they own, and can only monotonically increase their ``nice
the range 0 to PRIO_MAX (20). (This prevents overriding administrative
fiats.) The superuser may alter the priority of any process
and set the
priority to any value in the range PRIO_MIN (-20) to
priorities are: 20 (the affected processes will run only
else in the system wants to), 0 (the ``base'' scheduling
negative (to make things go very fast).
/etc/passwd for mapping user names to user IDs
nice(1), getpriority(2), setpriority(2)
The renice command appeared in 4.0BSD.
Non-superusers cannot increase scheduling priorities of
their own processes,
even if they were the ones that decreased the priorities in the
OpenBSD 3.6 June 9, 1993
[ Back ]