RENICE(1) | User Commands | RENICE(1) |
renice - alter priority of running processes
renice [-n increment] [-i idtype] ID...
renice [-n increment] [-g | -p | -u] ID...
renice priority [-p] pid... [-g gid]... [-p pid]...
[-u user]...
renice priority -g gid... [-g gid]... [-p pid]...
[-u user]...
renice priority -u user... [-g gid]... [-p pid]...
[-u user]...
The renice command alters the scheduling priority of one or more running processes. By default, the processes to be affected are specified by their process IDs.
If the first operand is a number within the valid range of priorities (−20 to 20), renice will treat it as a priority (as in all but the first synopsis form). Otherwise, renice will treat it as an ID (as in the first synopsis form).
Users other than the privileged user may only alter the priority of processes they own, and can only monotonically increase their "nice value" within the range 0 to 19. This prevents overriding administrative fiats. The privileged user may alter the priority of any process and set the priority to any 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),; and any negative value (to make things go very fast). 20 is an acceptable nice value, but will be rounded down to 19.
renice supports the following option features:
The following options are supported:
-g
-i
-n increment
-p
-u
The following operands are supported:
ID
priority
Example 1 Adjusting the scheduling priority of process IDs
Adjust the system scheduling priority so that process IDs 987 and 32 would have a lower scheduling priority:
example% renice -n 5 -p 987 32
Example 2 Adjusting the scheduling priority of group IDs
Adjust the system scheduling priority so that group IDs 324 and 76 would have a higher scheduling priority, if the user has the appropriate privileges to do so:
example% renice -n -4 -g 324 76
Example 3 Adjusting the scheduling priority of a user ID and user name
Adjust the system scheduling priority so that numeric user ID 8 and user sas would have a lower scheduling priority:
example% renice -n 4 -u 8 sas
See environ(7) for descriptions of the following environment variables that affect the execution of renice: LANG, LC_ALL, LC_CTYPE, LC_MESSAGES, and NLSPATH.
The following exit values are returned:
0
>0
/etc/passwd
See attributes(7) for descriptions of the following attributes:
ATTRIBUTE TYPE | ATTRIBUTE VALUE |
Interface Stability | Standard |
nice(1), passwd(1), priocntl(1), attributes(7), environ(7), standards(7)
The renice syntax
renice [-n increment] [-i idtype] ID ...
is preferred over the old syntax
renice [-n increment] [-g | -p| -u] ID ...
which is now obsolete.
If you make the priority very negative, then the process cannot be interrupted.
To regain control you must make the priority greater than 0.
Users other than the privileged user cannot increase scheduling priorities of their own processes, even if they were the ones that decreased the priorities in the first place.
The priocntl command subsumes the function of renice.
January 9, 2004 | OmniOS |