Home
Search all pages
Subjects
By activity
Professions, Sciences, Humanities, Business, ...
User Interface
Text-based, GUI, Audio, Video, Keyboards, Mouse, Images,...
Text Strings
Conversions, tests, processing, manipulation,...
Math
Integer, Floating point, Matrix, Statistics, Boolean, ...
Processing
Algorithms, Memory, Process control, Debugging, ...
Stored Data
Data storage, Integrity, Encryption, Compression, ...
Communications
Networks, protocols, Interprocess, Remote, Client Server, ...
Hard World Timing, Calendar and Clock, Audio, Video, Printer, Controls...
File System
Management, Filtering, File & Directory access, Viewers, ...
|
|
|
RocketLink!--> Man page versions:
OpenBSD
FreeBSD
NetBSD
Others
RENICE(8) OpenBSD System Manager's Manual RENICE(8)
NAME
renice - alter priority of running processes
SYNOPSIS
renice priority [[-p] pid ...] [[-g] pgrp ...] [[-u] user ...]
DESCRIPTION
Renice alters the scheduling priority (an integer) of one or more running
processes. The following who parameters (pid, pgrp and user) are inter-
preted as process ID's, process group ID's, 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. By default,
the processes to be affected are specified by their process ID's.
Options supported by renice:
-g Force who parameters to be interpreted as process group ID's.
-u Force the who parameters to be interpreted as user names.
-p Resets the who interpretation to be (the default) process ID's.
For example,
renice +1 987 -u daemon root -p 32
would change the priority of process ID's 987 and 32, and all processes
owned by users daemon and root.
Users other than the super-user may only alter the priority of processes
they own, and can only monotonically increase their ``nice value'' within
the range 0 to PRIO_MAX (20). (This prevents overriding administrative
fiats.) The super-user may alter the priority of any process and set the
priority to any value in the range PRIO_MIN (-20) to PRIO_MAX. Useful
priorities are: 20 (the affected processes will run only when nothing
else in the system wants to), 0 (the ``base'' scheduling priority), any-
thing negative (to make things go very fast).
FILES
/etc/passwd to map user names to user ID's
SEE ALSO
nice(1), getpriority(2), setpriority(2)
BUGS
Non super-users can not increase scheduling priorities of their own pro-
cesses, even if they were the ones that decreased the priorities in the
first place.
HISTORY
The renice command appeared in 4.0BSD.
4th Berkeley Distribution March 16, 1991 1
Source: OpenBSD 2.6 man pages. Copyright: Portions are copyrighted by BERKELEY SOFTWARE DESIGN, INC., The Regents of the University of California, Massachusetts Institute of Technology, Free Software Foundation, FreeBSD Inc., and others. |
(Corrections, notes, and links courtesy of RocketAware.com)
FreeBSD Sources for renice(8) OpenBSD sources for renice(8)
Up to: Process Creation and Control - child process control (like sending signals), renice, fork, et al
Up to: Process Limits: Resources - Process Limits on resource usage (disk, CPU, memory, et al)
RocketLink!--> Man page versions:
OpenBSD
FreeBSD
NetBSD
Others
Rapid-Links:
Search | About | Comments | Submit Path: RocketAware > man pages >
renice.8/
RocketAware.com is a service of Mib Software Copyright 1999, Forrest J. Cavalier III. All Rights Reserved. We welcome submissions and comments
|