version 1, including all changes.
.
Rev |
Author |
# |
Line |
1 |
perry |
1 |
---- |
|
|
2 |
__NAME__ |
|
|
3 |
|
|
|
4 |
|
|
|
5 |
renice - alter priority of running processes |
|
|
6 |
__SYNOPSIS__ |
|
|
7 |
|
|
|
8 |
|
|
|
9 |
renice priority [[ |
|
|
10 |
[[-p] |
|
|
11 |
pid ... |
|
|
12 |
] [[ [[-g] |
|
|
13 |
pgrp ... |
|
|
14 |
] [[ [[-u] |
|
|
15 |
user ... |
|
|
16 |
] |
|
|
17 |
__DESCRIPTION__ |
|
|
18 |
|
|
|
19 |
|
|
|
20 |
Renice alters the scheduling priority of one or more running |
|
|
21 |
processes. The following who parameters are interpreted as |
|
|
22 |
process ID's, process group ID's, or user names. Renice'ing |
|
|
23 |
a process group causes all processes in the process group to |
|
|
24 |
have their scheduling priority altered. Renice'ing a user |
|
|
25 |
causes all processes owned by the user to have their |
|
|
26 |
scheduling priority altered. By default, the processes to be |
|
|
27 |
affected are specified by their process ID's. |
|
|
28 |
|
|
|
29 |
|
|
|
30 |
Options supported by renice: |
|
|
31 |
-g Force who parameters to be interpreted as processgroup ID's. |
|
|
32 |
|
|
|
33 |
|
|
|
34 |
-uForce the who parameters to be interpreted as usernames.-pResets the who interpretation to be (the default)process ID's.For example,renice +1 987 -u daemon root -p 32 |
|
|
35 |
would change the priority of process ID's 987 and 32, and all processes owned by users daemon and root. |
|
|
36 |
|
|
|
37 |
|
|
|
38 |
Users other than the super-user may only alter the priority |
|
|
39 |
of processes they own, and can only monotonically increase |
|
|
40 |
their ``nice value'' within the range 0 to PRIO_MAX |
|
|
41 |
(20). (This prevents overriding administrative fiats.) The |
|
|
42 |
super-user may alter the priority of any process and set the |
|
|
43 |
priority to any value in the range PRIO_MIN (-20) |
|
|
44 |
to PRIO_MAX. Useful priorities are: 20 (the |
|
|
45 |
affected processes will run only when nothing else in the |
|
|
46 |
system wants to), 0 (the ``base'' scheduling priority), |
|
|
47 |
anything negative (to make things go very |
|
|
48 |
fast). |
|
|
49 |
__FILES__ |
|
|
50 |
/etc/passwd |
|
|
51 |
|
|
|
52 |
|
|
|
53 |
to map user names to user ID's |
|
|
54 |
|
|
|
55 |
|
|
|
56 |
__SEE ALSO__ |
|
|
57 |
|
|
|
58 |
|
|
|
59 |
getpriority(2), |
|
|
60 |
setpriority(2) |
|
|
61 |
__BUGS__ |
|
|
62 |
|
|
|
63 |
|
|
|
64 |
Non super-users can not increase scheduling priorities of |
|
|
65 |
their own processes, even if they were the ones that |
|
|
66 |
decreased the priorities in the first place. |
|
|
67 |
The Linux kernel (at least version 2.0.0) and linux libc (at |
|
|
68 |
least version 5.2.18) does not agree entierly on what the |
|
|
69 |
specifics of the systemcall interface to set nice values is. |
|
|
70 |
Thus causes renice to report bogus previous nice |
|
|
71 |
values. |
|
|
72 |
__HISTORY__ |
|
|
73 |
|
|
|
74 |
|
|
|
75 |
The renice command appeared in 4.0 BSD |
|
|
76 |
. |
|
|
77 |
|
|
|
78 |
|
|
|
79 |
4th Berkeley Distribution June 9, 1993 1 |
|
|
80 |
---- |