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