Resources usage can be limited using the setrlimit()
function
described below. Each resource is controlled by a pair of limits: a
soft limit and a hard limit. The soft limit is the current limit, and
may be lowered or raised by a process over time. The soft limit can
never exceed the hard limit. The hard limit can be lowered to any
value greater than the soft limit, but not raised. (Only processes with
the effective UID of the super-user can raise a hard limit.)
The specific resources that can be limited are system dependent. They
are described in the getrlimit()
man page. The resources
listed below are supported when the underlying operating system
supports them; resources which cannot be checked or controlled by the
operating system are not defined in this module for those platforms.
(soft, hard)
with the current
soft and hard limits of resource. Raises ValueError
if
an invalid resource is specified, or resource.error
if the
underyling system call fails unexpectedly.
(soft, hard)
of two
integers describing the new limits. A value of -1
can be used to
specify the maximum possible upper limit.
Raises ValueError
if an invalid resource is specified, if the new
soft limit exceeds the hard limit, or if a process tries to raise its
hard limit (unless the process has an effective UID of
super-user). Can also raise a resource.error
if the
underyling system call fails.
These symbols define resources whose consumption can be controlled
using the setrlimit()
and getrlimit()
functions defined
below. The values of these symbols are exactly the constants used
by C programs.
The Unix man page for getrlimit()
lists the available
resources. Note that not all systems use the same symbol or same
value to denote the same resource.
SIGXCPU
signal is sent to
the process. (See the signal
module documentation for
information about how to catch this signal and do something useful,
e.g. flush open files to disk.)
RLIMIT_NOFILE
.