1RENICE(8)                 BSD System Manager's Manual                RENICE(8)
2

NAME

4     renice — alter priority of running processes
5

SYNOPSIS

7     renice priority [[-p] pid ...] [[-g] pgrp ...] [[-u] user ...]
8

DESCRIPTION

10     Renice alters the scheduling priority of one or more running processes.
11     The following who parameters are interpreted as process ID's, process
12     group ID's, or user names.  Renice'ing a process group causes all pro‐
13     cesses in the process group to have their scheduling priority altered.
14     Renice'ing a user causes all processes owned by the user to have their
15     scheduling priority altered.  By default, the processes to be affected
16     are specified by their process ID's.
17
18     Options supported by renice:
19
20     -g      Force who parameters to be interpreted as process group ID's.
21
22     -u      Force the who parameters to be interpreted as user names.
23
24     -p      Resets the who interpretation to be (the default) process ID's.
25
26     For example,
27
28     renice +1 987 -u daemon root -p 32
29
30     would change the priority of process ID's 987 and 32, and all processes
31     owned by users daemon and root.
32
33     Users other than the super-user may only alter the priority of processes
34     they own, and can only monotonically increase their ``nice value'' within
35     the range 0 to PRIO_MAX (20).  (This prevents overriding administrative
36     fiats.)  The super-user may alter the priority of any process and set the
37     priority to any value in the range PRIO_MIN (-20) to PRIO_MAX.  Useful
38     priorities are: 20 (the affected processes will run only when nothing
39     else in the system wants to), 0 (the ``base'' scheduling priority), any‐
40     thing negative (to make things go very fast).
41

FILES

43     /etc/passwd  to map user names to user ID's
44

SEE ALSO

46     getpriority(2), setpriority(2)
47

BUGS

49     Non super-users can not increase scheduling priorities of their own pro‐
50     cesses, even if they were the ones that decreased the priorities in the
51     first place.
52     The Linux kernel (at least version 2.0.0) and linux libc (at least ver‐
53     sion 5.2.18) does not agree entirely on what the specifics of the system‐
54     call interface to set nice values is.  Thus causes renice to report bogus
55     previous nice values.
56

HISTORY

58     The renice command appeared in 4.0BSD.
59
604th Berkeley Distribution        June 9, 1993        4th Berkeley Distribution
Impressum