LDP
/
man-pages
mirror of https://github.com/mkerrisk/man-pages
0
1
Fork 0
Code Releases Activity

Added BUGS text on 2.6.x handling of RLIMIT_CPU limit 

of zero seconds.  See
http://marc.theaimsgroup.com/?l=linux-kernel&m=112256338703880&w=2
This commit is contained in:
Michael Kerrisk 2006-04-04 04:12:36 +00:00
parent 9aad1caae1
commit 6057e7a9fa
1 changed files with 10 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
man2/getrlimit.2
View File

@ -363,6 +363,16 @@ signals delivered when a process encountered the soft and hard
limits were delivered one (CPU) second later than they should have been.
This was fixed in kernel 2.6.8.
In 2.6.x kernels before 2.6.17, a
.B RLIMIT_CPU
limit of 0 is wrongly treated as "no limit" (like
.BR RLIM_INFINITY ).
.\" FIXME . The following change occurred in 2.6.17-rc1; verify
.\" that it stays for 2.6.17 final.
.\" see http://marc.theaimsgroup.com/?l=linux-kernel&m=114008066530167&w=2
Since kernel 2.6.17, setting a limit of 0 does have an effect,
but is actually treated as a limit of 1 second.
A kernel bug means that
.B RLIMIT_RTPRIO
does not work in kernel 2.6.12; the problem is fixed in kernel 2.6.13.