As discovered here today, the change in Kernel 2.6.17 intended to inhibit users from setting RLIMIT_CPU to 0 (as that is equivalent to unlimited) by "cheating" and setting it to 1 in such a case, does not make a difference, as the check is done in the wrong place (too late), and only applies to the profiling code. Bugs: https://launchpad.net/bugs/107209 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=419706 Fixed in 2.6.22: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=9926e4c74300c4b31dee007298c6475d33369df0
proposed [linux >= 2.6.17 < 2.6.22] 9926e4c74300c4b31dee007298c6475d33369df0
sounds good :-)