1RENICE(1)                        User Commands                       RENICE(1)
2
3
4

NAME

6       renice - alter priority of running processes
7

SYNOPSIS

9       renice [-n] priority [-gpu] identifier...
10

DESCRIPTION

12       renice alters the scheduling priority of one or more running processes.
13       The first argument is the priority value to be used.  The  other  argu‐
14       ments  are  interpreted as process IDs (by default), process group IDs,
15       user IDs, or user names.  renice'ing a process group  causes  all  pro‐
16       cesses  in the process group to have their scheduling priority altered.
17       renice'ing a user causes all processes owned by the user to have  their
18       scheduling priority altered.
19

OPTIONS

21       -n, --priority priority
22              Specify  the  scheduling  priority  to  be used for the process,
23              process group, or user.  Use of the option -n or  --priority  is
24              optional, but when used it must be the first argument.
25
26       -g, --pgrp pgid...
27              Force  the  succeeding  arguments  to  be interpreted as process
28              group IDs.
29
30       -u, --user name_or_uid...
31              Force the succeeding arguments to be interpreted as usernames or
32              UIDs.
33
34       -p, --pid pid...
35              Force  the succeeding arguments to be interpreted as process IDs
36              (the default).
37
38       -h, --help
39              Display a help text.
40
41       -V, --version
42              Display version information.
43

EXAMPLES

45       The following command would change the priority of the  processes  with
46       PIDs 987 and 32, plus all processes owned by the users daemon and root:
47
48              renice +1 987 -u daemon root -p 32
49

NOTES

51       Users  other  than  the  super-user may only alter the priority of pro‐
52       cesses they own, and  can  only  monotonically  increase  their  ``nice
53       value''  (for  security  reasons)  within the range 0 to PRIO_MAX (20),
54       unless a nice resource limit is set (Linux  2.6.12  and  higher).   The
55       super-user  may  alter the priority of any process and set the priority
56       to any value in the range PRIO_MIN (-20) to PRIO_MAX.   Useful  priori‐
57       ties are: 20 (the affected processes will run only when nothing else in
58       the system wants to), 0 (the ``base''  scheduling  priority),  anything
59       negative (to make things go very fast).
60

FILES

62       /etc/passwd
63              to map user names to user IDs
64

SEE ALSO

66       getpriority(2), setpriority(2)
67

BUGS

69       Non  super-users  can  not  increase scheduling priorities of their own
70       processes, even if they were the ones that decreased the priorities  in
71       the first place.
72
73       The Linux kernel (at least version 2.0.0) and linux libc (at least ver‐
74       sion 5.2.18) does not agree entirely on what the specifics of the  sys‐
75       temcall  interface to set nice values is.  Thus causes renice to report
76       bogus previous nice values.
77

HISTORY

79       The renice command appeared in 4.0BSD.
80

AVAILABILITY

82       The renice command is part of the util-linux package and  is  available
83       from  Linux  Kernel Archive ⟨ftp://ftp.kernel.org/pub/linux/utils/util-
84       linux/⟩.
85
86
87
88util-linux                      September 2011                       RENICE(1)
Impressum