The maximum size of the process's data segment (initialized data,
uninitialized data, and heap).
This limit affects calls to
-.BR brk ()
+.BR brk (2)
and
-.BR sbrk (),
+.BR sbrk (2),
which fail with the error
.B ENOMEM
upon encountering the soft limit of this resource.
signal.
By default, this signal terminates a process, but a process can
catch this signal instead, in which case the relevant system call (e.g.,
-.BR write ()
-.BR truncate ())
+.BR write (2)
+.BR truncate (2))
fails with the error
.BR EFBIG .
.TP
.BR RLIMIT_LOCKS " (Early Linux 2.4 only)"
.\" to be precise: Linux 2.4.0-test9; no longer in 2.4.25 / 2.5.65
A limit on the combined number of
-.BR flock ()
+.BR flock (2)
locks and
-.BR fcntl ()
+.BR fcntl (2)
leases that this process may establish.
.TP
.B RLIMIT_MEMLOCK
is the
.I mq_attr
structure specified as the fourth argument to
-.BR mq_open ().
+.BR mq_open (3).
The first addend in the formula, which includes
.I "sizeof(struct msg_msg *)"
Specifies a value one greater than the maximum file descriptor number
that can be opened by this process.
Attempts
-.RB ( open (),
-.BR pipe (),
-.BR dup (),
+.RB ( open (2),
+.BR pipe (2),
+.BR dup (2),
etc.)
to exceed this limit yield the error
.BR EMFILE .
The maximum number of processes (or, more precisely on Linux, threads)
that can be created for the real user ID of the calling process.
Upon encountering this limit,
-.BR fork ()
+.BR fork (2)
fails with the error
.BR EAGAIN .
.TP
(the number of virtual pages resident in RAM).
This limit only has effect in Linux 2.4.x, x < 30, and there only
affects calls to
-.BR madvise ()
+.BR madvise (2)
specifying
.BR MADV_WILLNEED .
.\" As at kernel 2.6.12, this limit still does nothing in 2.6 though