Museum

Home

Lab Overview

Retrotechnology Articles

Online Manuals

⇒ renice(1M) — IRIX 6.5.3f

Media Vault

Software Library

Restoration Projects

Artifacts Sought

Related Articles

getpriority(2)

setpriority(2)



renice(1M)                                                          renice(1M)



NAME
     renice - alter priority of running processes

SYNOPSIS
     /etc/renice [ -n increment | priority ] [ [ -p ] pid ... ]
          [ [ -g ] pgrp ... ] [ [ -u ] user ... ]

DESCRIPTION
     renice alters the scheduling priority of one or more running processes.
     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.

     The -n increment specifies how the system scheduling priority of the
     specified process(es) is to be adjusted.  The increment option-argument
     is a positive or negative decimal integer that is used to modify the
     system scheduling priority of the specified process(es).  The priority
     value is taken as the actual system scheduling priority, rather than as
     an increment to the existing scheduling priority.

     The parameters are interpreted as process ID's, process group ID's, or
     user names as follows.  By default, the processes to be affected are
     specified by their process ID's.  To force parameters to be interpreted
     as process group ID's, the -g option can be used.  To force the
     parameters to be interpreted as user names, the -u option can be used.
     Supplying -p resets interpretation to be (the default) process ID's.  For
     example,

          /etc/renice +1 987 -u daemon root -p 32

     changes the priority of process ID's 987 and 32, and all processes owned
     by users daemon and root.

     Users other than the superuser can 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 superuser can 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 run only when nothing else in the system
          wants to.

     0    The ``base'' scheduling priority.

     anything negative
          Make things go very fast.

FILES
     /etc/passwd     to map user names to user ID's





                                                                        Page 1





renice(1M)                                                          renice(1M)



SEE ALSO
     getpriority(2), setpriority(2).





















































                                                                        Page 2



Typewritten Software • bear@typewritten.org • Edmonds, WA 98026