Differences between current version and predecessor to the previous major change of nice(2).

Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History

Newer page: version 8 Last edited on Wednesday, June 15, 2005 4:55:16 pm by SidSwami
Older page: version 3 Last edited on Sunday, March 16, 2003 5:54:09 pm by PerryLorier Revert
@@ -9,18 +9,17 @@
 nice(2) adds ''inc'' to the nice value for the calling pid. (A large nice value means a low priority.) Only the super- user may specify a negative increment, or 
 priority increase. 
-On success, zero is returned. On error, -1 is returned, and ''errno'' is set appropriately
+On success, the new nice variable is returned. On failure -1 is returned. Since -1 is a valid return for nice(2), set errno(3) to 0 before calling nice(2), and check its value afterwards if nice(2) returns a value of -1
 ;[EPERM]: A non-super user attempts to do a priority increase by supplying a negative ''inc''. 
-Note that the routine is documented in SUSv2 to return the new nice value, while the Linux syscall and (g)libc (earlier than glibc 2.2.4) routines return 0 on success. The new nice value can be found using getpriority(2). Note that an implementation in which __nice__ returns the new nice value can legitimately return -1. To reliably detect an  
-error, set ''errno'' to 0 before the call, and check its value when __nice__ returns -1
+Older (g)libc (earlier than glibc 2.2.4) return 0 on success, and the new nice value should be found by calling getpriority(2). 
-nice(1), getpriority(2), setpriority(2), fork(2), renice(1) 
+nice(1), getpriority(2), setpriority(2), fork(2), renice(1), sched_getscheduler(2), sched_getparam(2
This page is a man page (or other imported legacy content). We are unable to automatically determine the license status of this page.