From 6057e7a9fa8d8bd9040943bc4bf2bd5be3970bcc Mon Sep 17 00:00:00 2001
From: Michael Kerrisk <mtk.manpages@gmail.com>
Date: Tue, 4 Apr 2006 04:12:36 +0000
Subject: [PATCH] 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

---
 man2/getrlimit.2 | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/man2/getrlimit.2 b/man2/getrlimit.2
index 5ce006800..f7d418f6f 100644
--- a/man2/getrlimit.2
+++ b/man2/getrlimit.2
@@ -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.