getpriority.2: Clarify equivalence between lower nice value and higher priority

Reported-by: Robin Kuzmin <kuzmin.robin@gmail.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk 2016-07-02 00:36:43 +02:00
parent 653c1fe2e2
commit b8bc577b89
1 changed files with 5 additions and 2 deletions

View File

@ -90,11 +90,13 @@ A zero value for
.I who
denotes (respectively) the calling process, the process group of the
calling process, or the real user ID of the calling process.
The
.I prio
argument is a value in the range \-20 to 19 (but see NOTES below).
with \-20 being the highest priority and 19 being the lowest priority.
The default priority is 0;
lower priorities cause more favorable scheduling.
lower values give a process a higher scheduling priority.
The
.BR getpriority ()
@ -140,7 +142,8 @@ In addition to the errors indicated above,
may fail if:
.TP
.B EACCES
The caller attempted to lower a process priority, but did not
The caller attempted to set a lower nice value
(i.e., a higher process priority), but did not
have the required privilege (on Linux: did not have the
.B CAP_SYS_NICE
capability).