Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

nice(1) [opendarwin man page]

NICE(1) 						    BSD General Commands Manual 						   NICE(1)

nice -- execute a utility at an altered scheduling priority SYNOPSIS
nice [-n increment] utility [argument ...] DESCRIPTION
The nice utility runs utility at an altered scheduling priority, by incrementing its ``nice'' value by the specified increment, or a default value of 10. The lower the nice value of a process, the higher its scheduling priority. The superuser may specify a negative increment in order to run a utility with a higher scheduling priority. Some shells may provide a builtin nice command which is similar or identical to this utility. Consult the builtin(1) manual page. ENVIRONMENT
The PATH environment variable is used to locate the requested utility if the name contains no '/' characters. EXAMPLES
Execute utility 'date' at priority 5 assuming the priority of the shell is 0: nice -n 5 date Execute utility 'date' at priority -19 assuming the priority of the shell is 0 and you are the super-user: nice -n 16 nice -n -35 date DIAGNOSTICS
If utility is invoked, the exit status of nice is the exit status of utility. An exit status of 126 indicates utility was found, but could not be executed. An exit status of 127 indicates utility could not be found. SEE ALSO
builtin(1), csh(1), idprio(1), rtprio(1), getpriority(2), setpriority(2), renice(8) COMPATIBILITY
The traditional -increment option has been deprecated but is still supported. STANDARDS
The nice utility conforms to IEEE Std 1003.1-2001 (``POSIX.1''). HISTORY
A nice utility appeared in Version 4 AT&T UNIX. BSD
June 6, 1993 BSD

Check Out this Related Man Page

RENICE(8)						    BSD System Manager's Manual 						 RENICE(8)

renice -- alter priority of running processes SYNOPSIS
renice priority [[-p] pid ...] [[-g] pgrp ...] [[-u] user ...] renice -n increment [[-p] pid ...] [[-g] pgrp ...] [[-u] user ...] DESCRIPTION
The renice utility alters the scheduling priority of one or more running processes. The following who parameters are interpreted as process ID's, process group ID's, user ID's or user names. The renice'ing of a process group causes all processes in the process group to have their scheduling priority altered. The renice'ing of 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. The following options are available: -g Force who parameters to be interpreted as process group ID's. -n Instead of changing the specified processes to the given priority, interpret the following argument as an increment to be applied to the current priority of each process. -u Force the who parameters to be interpreted as user names or user ID's. -p Reset the who interpretation to be (the default) process ID's. 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), anything negative (to make things go very fast). FILES
/etc/passwd to map user names to user ID's EXAMPLES
Change the priority of process ID's 987 and 32, and all processes owned by users daemon and root. renice +1 987 -u daemon root -p 32 SEE ALSO
nice(1), rtprio(1), getpriority(2), setpriority(2) STANDARDS
The renice utility conforms to IEEE Std 1003.1-2001 (``POSIX.1''). HISTORY
The renice utility appeared in 4.0BSD. BUGS
Non super-users cannot increase scheduling priorities of their own processes, even if they were the ones that decreased the priorities in the first place. BSD
June 9, 1993 BSD
Man Page

Featured Tech Videos