Return to renice.8 CVS log

Up to [Power 6/32 Unix Tahoe 4.2BSD] / cci / usr / src / man / man8

Annotation of cci/usr/src/man/man8/renice.8, revision 1.1.1.1

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

This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.