renice alters the scheduling priority of one or more running
processes. The first argument is the priority value to be used. The
other arguments are interpreted as process IDs (by default), process
group IDs, user IDs, or user names. renice'ing a process group
causes all processes in the process group to have their scheduling
priority altered. renice'ing a user causes all processes owned by
the user to have their scheduling priority altered.
-n, --priority priority
Specify the scheduling priority to be used for the process,
process group, or user. Use of the option -n or --priority is
optional, but when used it must be the first argument.
Interpret the succeeding arguments as process group IDs.
Interpret the succeeding arguments as process IDs (the
Interpret the succeeding arguments as usernames or UIDs.
Display version information and exit.
Display help text and exit.
Users other than the superuser may only alter the priority of
processes they own, and can only monotonically increase their ``nice
value'' (for security reasons) within the range 0 to 19, unless a
nice resource limit is set (Linux 2.6.12 and higher). The superuser
may alter the priority of any process and set the priority to any
value in the range -20 to 19. Useful priorities are: 19 (the
affected processes will run only when nothing else in the system
wants to), 0 (the ``base'' scheduling priority), anything negative
(to make things go very fast).
Non-superusers cannot increase scheduling priorities of their own
processes, even if they were the ones that decreased the priorities
in the first place.
The Linux kernel (at least version 2.0.0) and linux libc (at least
version 5.2.18) does not agree entirely on what the specifics of the
systemcall interface to set nice values is. Thus causes renice to
report bogus previous nice values.
This page is part of the util-linux (a random collection of Linux
utilities) project. Information about the project can be found at
⟨https://www.kernel.org/pub/linux/utils/util-linux/⟩. If you have a
bug report for this manual page, send it to
firstname.lastname@example.org. This page was obtained from the
project's upstream Git repository
2016-10-04. If you discover any rendering problems in this HTML ver‐
sion of the page, or you believe there is a better or more up-to-date
source for the page, or you have corrections or improvements to the
information in this COLOPHON (which is not part of the original man‐
ual page), send a mail to email@example.com
util-linux July 2014 RENICE(1)