1GETPRIORITY(2) Linux Programmer's Manual GETPRIORITY(2)
2
6 getpriority, setpriority - get/set program scheduling priority
7
9 #include <sys/time.h>
10 #include <sys/resource.h>
11 int getpriority(int which, int who);
13 int setpriority(int which, int who, int prio);
14
16 The scheduling priority of the process, process group, or user, as
17 indicated by which and who is obtained with the getpriority() call and
18 set with the setpriority() call.
19 The value which is one of PRIO_PROCESS, PRIO_PGRP, or PRIO_USER, and
21 who is interpreted relative to which (a process identifier for
22 PRIO_PROCESS, process group identifier for PRIO_PGRP, and a user ID for
23 PRIO_USER). A zero value for who denotes (respectively) the calling
24 process, the process group of the calling process, or the real user ID
25 of the calling process. Prio is a value in the range -20 to 19 (but
26 see the Notes below). The default priority is 0; lower priorities
27 cause more favorable scheduling.
28 The getpriority() call returns the highest priority (lowest numerical
30 value) enjoyed by any of the specified processes. The setpriority()
31 call sets the priorities of all of the specified processes to the spec‐
32 ified value. Only the superuser may lower priorities.
33
35 Since getpriority() can legitimately return the value -1, it is neces‐
36 sary to clear the external variable errno prior to the call, then check
37 it afterwards to determine if a -1 is an error or a legitimate value.
38 The setpriority() call returns 0 if there is no error, or -1 if there
39 is.
40
42 EINVAL which was not one of PRIO_PROCESS, PRIO_PGRP, or PRIO_USER.
43 ESRCH No process was located using the which and who values specified.
45 In addition to the errors indicated above, setpriority() may fail if:
47 EPERM A process was located, but its effective user ID did not match
49 either the effective or the real user ID of the caller, and was
50 not privileged (on Linux: did not have the CAP_SYS_NICE capabil‐
51 ity). But see NOTES below.
52 EACCES The caller attempted to lower a process priority, but did not
54 have the required privilege (on Linux: did not have the
55 CAP_SYS_NICE capability). Since Linux 2.6.12, this error only
56 occurs if the caller attempts to set a process priority outside
57 the range of the RLIMIT_NICE soft resource limit of the target
58 process; see getrlimit(2) for details.
59
61 A child created by fork(2) inherits its parent's nice value. The nice
62 value is preserved across execve(2).
63 The details on the condition for EPERM depend on the system. The above
65 description is what POSIX.1-2001 says, and seems to be followed on all
66 System V-like systems. Linux kernels before 2.6.12 required the real
67 or effective user ID of the caller to match the real user of the
68 process who (instead of its effective user ID). Linux 2.6.12 and later