From e6c5832f1973a124e8622532cb446296c492b69a Mon Sep 17 00:00:00 2001
From: Michael Kerrisk <mtk.manpages@gmail.com>
Date: Fri, 3 Dec 2004 16:06:22 +0000
Subject: [PATCH] Rewrote discussion on RLIMIT_MEMLOCK to incorporate kernel
 2.6.9 changes. Added note on RLIMIT_CPU error in older kernels. Added
 RLIMIT_SIGPENDING

---
 man2/getrlimit.2 | 23 +++++++++++++++++++----
 1 file changed, 19 insertions(+), 4 deletions(-)

diff --git a/man2/getrlimit.2 b/man2/getrlimit.2
index b191b7cff..8d42af983 100644
--- a/man2/getrlimit.2
+++ b/man2/getrlimit.2
@@ -55,6 +55,8 @@
 .\"	Rewrote discussion on RLIMIT_MEMLOCK to incorporate kernel
 .\"		2.6.9 changes.
 .\"	Added note on RLIMIT_CPU error in older kernels
+.\" 2004-11-03, mtk
+.\"	Added RLIMIT_SIGPENDING
 .\"
 .TH GETRLIMIT 2 2004-06-16 "Linux" "Linux Programmer's Manual"
 .SH NAME
@@ -150,7 +152,7 @@ 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
-.BR SIGXCPU ).
+.BR SIGXCPU .)
 .TP
 .B RLIMIT_DATA
 The maximum size of the process's data segment (initialized data,
@@ -199,7 +201,7 @@ operation, where it sets a maximum on the total bytes in
 shared memory segments (see
 .BR shmget (2))
 that may be locked by the real user ID of the calling process.
-(The 
+The 
 .BR shmctl (2)
 .B SHM_LOCK
 locks are accounted for separately from the per-process memory
@@ -209,14 +211,13 @@ and
 .BR mmap (2)
 .BR MAP_LOCKED ;
 a process can lock bytes up to this limit in each of these
-two categories.)
+two categories.
 In Linux kernels before 2.6.9, this limit controlled the amount of
 memory that could be locked by a privileged process.
 Since Linux 2.6.9, no limits are placed on the amount of memory
 that a privileged process may lock, and this limit instead governs
 the amount of memory that an unprivileged process may lock.
 .\" FIXME Linux 2.6.8 adds RLIMIT_MSGQUEUE
-.\" FIXME Linux 2.6.8 adds RLIMIT_SIGPENDING
 .TP
 .B RLIMIT_NOFILE
 Specifies a value one greater than the maximum file descriptor number
@@ -245,6 +246,16 @@ specifying
 .\" As at kernel 2.6.9, this limit still does nothing in 2.6 though
 .\" talk of making it do something continues in LKML -- MTK, Nov 04
 .TP
+.B RLIMIT_SIGPENDING
+Specifies the limit on the number of real-time signals (see
+.BR sigqueue (2)
+and 
+.BR signal (7))
+that may be queued for the real user ID of the calling process.
+(Since Linux 2.6.8.)
+.\" This replaces the /proc/sys/kernel/rtsig-max system-wide limit
+.\" that was present in kernels <= 2.6.7.  MTK Dec 04
+.TP
 .B RLIMIT_STACK
 The maximum size of the process stack, in bytes.
 Upon reaching this limit, a
@@ -297,6 +308,9 @@ they are present on the BSDs and Linux, but on few other implementations.
 .BR RLIMIT_RSS
 derives from BSD and is not specified in POSIX.1-2001;
 it is nevertheless present on most implementations.
+.B RLIMIT_SIGPENDING
+is Linux specific.
+.\" FIXME RLIMIT_MSGQUEUE is also Linux specific.
 .SH "SEE ALSO"
 .BR dup (2),
 .BR fcntl (2),
@@ -308,6 +322,7 @@ it is nevertheless present on most implementations.
 .BR quotactl (2),
 .BR sbrk (2),
 .BR shmctl (2),
+.BR sigqueue (2),
 .BR malloc (3),
 .BR ulimit (3),
 .BR capabilities (7),