man getrlimit(2) not updated for Linux 3.0

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

>From man 2 getrlimit:

              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
              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
              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.

Ryan Mullen
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at

[Netdev]     [Linux Ethernet Bridging]     [Linux Wireless]     [Kernel Newbies]     [Memory]     [Security]     [Linux for Hams]     [Netfilter]     [Bugtraq]     [Photo]     [Yosemite]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Admin]     [Samba]     [Video 4 Linux]     [Linux Resources]

Add to Google Powered by Linux