nice(3ucb) [opensolaris man page]

nice(3UCB)					     SunOS/BSD Compatibility Library Functions						nice(3UCB)

NAME

       nice - change priority of a process

SYNOPSIS

       /usr/ucb/cc [ flag ... ] file ...
       #include<unistd.h>

       int nice(incr)
       int incr;

DESCRIPTION

       The  scheduling	priority of the process is augmented by incr. Positive priorities get less service than normal. Priority 10 is recommended
       to users who wish to execute long-running programs without undue impact on system performance.

       Negative increments are illegal, except when specified by the privileged user. The priority is limited to the range -20 (most urgent) to 20
       (least). Requests for values above or below these limits result in the scheduling priority being set to the corresponding limit.

       The  priority  of  a process is passed to a child process by fork(2). For a privileged process to return to normal priority from an unknown
       state, nice() should be called successively with arguments -40 (goes to priority -20 because of truncation), 20 (to get to 0), then  0  (to
       maintain compatibility with previous versions of this call).

RETURN VALUES

       Upon successful completion, nice() returns 0. Otherwise, a value of -1 is returned and errno is set to indicate the error.

ERRORS

       The priority is not changed if:

       EPERM	The value of incr specified was negative, and the effective user ID is not the privileged user.

SEE ALSO

       cc(1B), nice(1), renice(1), fork(2), priocntl(2), getpriority(3C)

NOTES

       Use of these interfaces should be restricted to only applications written on BSD platforms.  Use of these interfaces with any of the system
       libraries or in multi-threaded applications is unsupported.

SunOS 5.11							    30 Oct 2007 							nice(3UCB)

nice(2) 							System Calls Manual							   nice(2)

NAME

       nice - change priority of a process

SYNOPSIS

DESCRIPTION

       adds  the  value  of  priority_change to the nice value of the calling process.	A process's is a positive number for which a more positive
       value results in lower CPU priority.

       A maximum nice value of 39 and a minimum nice value of 0 are imposed by the system.  Requests for values above or below these limits result
       in the nice value being set to the corresponding limit.

       If the calling process contains more than one thread or lightweight process (i.e., the process is multi-threaded) this function shall apply
       to all threads or lightweight processes in the calling process.

   Security Restrictions
       Some or all of the actions associated with this system call are subject to compartmental restrictions. See compartments(5) for more  infor-
       mation  about  compartmentalization on systems that support that feature.  Compartmental restrictions can be overridden if the process pos-
       sesses the privilege (COMMALLOWED).  Processes owned by the superuser may not have this privilege.  Processes owned by any  user  may  have
       this privilege, depending on system configuration.

       Some  or  all  of  the  actions associated with this system call require the (OWNER) and/or the (LIMIT) privileges.  Processes owned by the
       superuser will have these privileges.  Processes owned by other users may have privilege(s), depending on system configuration.	See privi-
       leges(5) for more information about privileged access on systems that support fine-grained privileges.

RETURN VALUE

       Upon successful completion, returns the new nice value minus 20.  Otherwise, a value of -1 is returned and is set to indicate the error.

       Note that assumes a user process priority value of 20.  If a user having appropriate privileges has changed the user process priority value
       to something less than 20, certain values for priority_change can cause to return -1, which is indistinguishable from an error return.

ERRORS

       [EPERM]	      fails and does not change the nice value if priority_change is negative or greater than 40, and the effective user ID of the
		      calling process is not a user having appropriate privileges.

SEE ALSO

       nice(1), renice(1M), exec(2), privileges(5).

STANDARDS CONFORMANCE

																	   nice(2)