Commit | Line | Data |
---|---|---|
f56e8d15 KB |
1 | .\" Copyright (c) 1983 The Regents of the University of California. |
2 | .\" All rights reserved. | |
c229b29d | 3 | .\" |
c45a9e4d | 4 | .\" %sccs.include.redist.man% |
c229b29d | 5 | .\" |
c45a9e4d | 6 | .\" @(#)renice.8 6.4 (Berkeley) %G% |
f56e8d15 KB |
7 | .\" |
8 | .UC 7 | |
0b8cdd44 | 9 | .TH RENICE 8 "" |
c229b29d KM |
10 | .UC 4 |
11 | .SH NAME | |
8d36c088 | 12 | renice \- alter priority of running processes |
c229b29d | 13 | .SH SYNOPSIS |
c45a9e4d | 14 | .B renice |
8d36c088 KM |
15 | priority [ [ |
16 | .B \-p | |
17 | ] pid ... ] [ [ | |
18 | .B \-g | |
19 | ] pgrp ... ] [ [ | |
20 | .B \-u | |
21 | ] user ... ] | |
c229b29d KM |
22 | .SH DESCRIPTION |
23 | .I Renice | |
8d36c088 KM |
24 | alters the |
25 | scheduling priority of one or more running processes. | |
26 | The | |
27 | .I who | |
28 | parameters are interpreted as process ID's, process group | |
29 | ID's, or user names. | |
30 | .IR Renice 'ing | |
31 | a process group causes all processes in the process group | |
32 | to have their scheduling priority altered. | |
33 | .IR Renice 'ing | |
34 | a user causes all processes owned by the user to have | |
35 | their scheduling priority altered. | |
36 | By default, the processes to be affected are specified by | |
37 | their process ID's. To force | |
38 | .I who | |
39 | parameters to be interpreted as process group ID's, a | |
40 | .B \-g | |
41 | may be specified. To force the | |
42 | .I who | |
43 | parameters to be interpreted as user names, a | |
44 | .B \-u | |
45 | may be given. Supplying | |
46 | .B \-p | |
47 | will reset | |
48 | .I who | |
49 | interpretation to be (the default) process ID's. | |
50 | For example, | |
51 | .sp | |
c45a9e4d | 52 | renice +1 987 -u daemon root -p 32 |
8d36c088 KM |
53 | .sp |
54 | would change the priority of process ID's 987 and 32, and | |
55 | all processes owned by users daemon and root. | |
c229b29d | 56 | .PP |
8d36c088 KM |
57 | Users other than the super-user may only alter the priority of |
58 | processes they own, | |
59 | and can only monotonically increase their ``nice value'' | |
2b0388bc | 60 | within the range 0 to PRIO_MAX (20). |
8d36c088 KM |
61 | (This prevents overriding administrative fiats.) |
62 | The super-user | |
63 | may alter the priority of any process | |
2b0388bc MK |
64 | and set the priority to any value in the range PRIO_MIN (\-20) |
65 | to PRIO_MAX. | |
8d36c088 | 66 | Useful priorities are: |
2b0388bc | 67 | 20 (the affected processes will run only when nothing else |
8d36c088 KM |
68 | in the system wants to), |
69 | 0 (the ``base'' scheduling priority), | |
70 | anything negative (to make things go very fast). | |
c229b29d | 71 | .SH FILES |
8d36c088 | 72 | /etc/passwd to map user names to user ID's |
c229b29d | 73 | .SH SEE ALSO |
8d36c088 | 74 | getpriority(2), setpriority(2) |
c229b29d | 75 | .SH BUGS |
8d36c088 KM |
76 | Non super-users can not increase scheduling priorities of their own processes, |
77 | even if they were the ones that decreased the priorities in the first place. |