Hello Ryan, On Sat, Jul 30, 2011 at 3:27 AM, Ryan Mullen <rmmullen@xxxxxxxxx> wrote: > From man 2 getrlimit: > > RLIMIT_CPU > CPU time limit in seconds. When the process reaches > the soft limit, it is sent a SIGXCPU signal. The default action for > this signal is to terminate the process. However, the signal can be > caught, > and the handler can return control to the main program. > If the process continues to consume CPU time, it will be sent SIGXCPU > once per second until the hard limit is reached, at which time it is > sent > SIGKILL. (This latter point describes Linux 2.2 > through 2.6 behavior. Implementations vary in how they treat > processes which continue to consume CPU time after reaching the soft > limit. Portable > applications that need to catch this signal should > perform an orderly termination upon first receipt of SIGXCPU.) > > > Instead of defining a window between Linux 2.2 and 2.6, can we not say > "This latter point describes behavior since Linux 2.2" to avoid the > versioning headaches, especially now that we're on 3.0? Note that I > haven't confirmed whether this behavior has changed for 3.0 - I'm > expecting it hasn't. Thanks for the report. What I did was to remove all mention of versions, since the behavior applies since at least 2.2, but probably earlier also. The change will be in man-pages-3.33. Cheers, Michael -- Michael Kerrisk Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ Author of "The Linux Programming Interface"; http://man7.org/tlpi/ -- To unsubscribe from this list: send the line "unsubscribe linux-man" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
