MirOS Manual: nice(1)

NICE(1)                      BSD Reference Manual                      NICE(1)


     nice - execute a utility with an altered scheduling priority


     nice [-n increment] utility [argument ...]


     nice runs utility at an altered scheduling priority. If an increment is
     given, it is used; otherwise an increment of 10 is assumed. The superuser
     can run utilities with priorities higher than normal by using a negative
     increment. The priority can be adjusted over a range of -20 (the highest)
     to 20 (the lowest).

     The options are as follows:

     -n increment
             A positive or negative decimal integer used to modify the system
             scheduling priority of utility.

     The nice utility shall exit with one of the following values:

           1-125   An error occurred.
           126     The utility was found but could not be invoked.
           127     The utility could not be found.

     Otherwise, the exit status of nice shall be that of utility.


     csh(1), getpriority(2), setpriority(2), renice(8)


     The historic -increment option has been deprecated but is still supported
     in this implementation.

     The nice utility conforms to IEEE Std 1003.2-1992 ("POSIX.2").


     A nice utility appeared in Version 6 AT&T UNIX.


     nice is built into csh(1) with a slightly different syntax than described
     here. The form 'nice +10' nices to positive nice, and 'nice -10' can be
     used by the superuser to give a process more of the processor.

MirOS BSD #10-current            June 6, 1993                                1

Generated on 2017-04-03 16:26:17 by $MirOS: src/scripts/roff2htm,v 1.88 2017/01/29 00:51:06 tg Exp $

These manual pages and other documentation are copyrighted by their respective writers; their source is available at our CVSweb, AnonCVS, and other mirrors. The rest is Copyright © 2002–2017 The MirOS Project, Germany.
This product includes material provided by mirabilos.

This manual page’s HTML representation is supposed to be valid XHTML/1.1; if not, please send a bug report — diffs preferred.