UNIX ON-LINE Man Pages - Die Onlinehilfe

Die Syntax von Unixbefehlen wird in den entsprechenden Manpages dokumentiert. Hier können Sie diese Onlinehilfe für viele Standardbefehle abrufen.

Seiten auflisten, welche beginnen mit:
A   B   C   D   E   F   G   H   I   J   K   L   M   N   O   P   Q   R   S   T   U   V   W   X   Y   Z   ALPHA   NUM   ANDERE   ALLE
GETRLIMIT(2)               Linux Programmer's Manual              GETRLIMIT(2)

       getrlimit, setrlimit - get/set resource limits

       #include <sys/time.h>
       #include <sys/resource.h>

       int getrlimit(int resource, struct rlimit *rlim);
       int setrlimit(int resource, const struct rlimit *rlim);

       getrlimit()  and  setrlimit() get and set resource limits respectively.
       Each resource has an associated soft and hard limit, as defined by  the
       rlimit  structure  (the  rlim  argument  to  both getrlimit() and setr-

           struct rlimit {
               rlim_t rlim_cur;  /* Soft limit */
               rlim_t rlim_max;  /* Hard limit (ceiling for rlim_cur) */

       The soft limit is the value that the kernel  enforces  for  the  corre-
       sponding  resource.   The  hard  limit  acts  as a ceiling for the soft
       limit: an unprivileged process may only set its soft limit to  a  value
       in  the range from 0 up to the hard limit, and (irreversibly) lower its
       hard  limit.   A  privileged  process  (under  Linux:  one   with   the
       CAP_SYS_RESOURCE capability) may make arbitrary changes to either limit

       The value RLIM_INFINITY denotes no limit on a  resource  (both  in  the
       structure  returned by getrlimit() and in the structure passed to setr-

       resource must be one of:

              The maximum size of the process's virtual memory (address space)
              in  bytes.   This  limit  affects  calls  to brk(2), mmap(2) and
              mremap(2), which fail with the error ENOMEM upon exceeding  this
              limit.  Also automatic stack expansion will fail (and generate a
              SIGSEGV that kills the process if no alternate  stack  has  been
              made  available via sigaltstack(2)).  Since the value is a long,
              on machines with a 32-bit long either this limit is  at  most  2
              GiB, or this resource is unlimited.

              Maximum  size  of core file.  When 0 no core dump files are cre-
              ated.  When nonzero, larger dumps are truncated to this size.

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

              The  maximum  size  of  the  process's data segment (initialized
              data, uninitialized data, and heap).  This limit  affects  calls
              to  brk(2)  and  sbrk(2),  which fail with the error ENOMEM upon
              encountering the soft limit of this resource.

              The maximum size of files that the process may create.  Attempts
              to  extend  a  file  beyond  this  limit result in delivery of a
              SIGXFSZ 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., write(2),  truncate(2))  fails  with
              the error EFBIG.

       RLIMIT_LOCKS (Early Linux 2.4 only)
              A  limit  on  the combined number of flock(2) locks and fcntl(2)
              leases that this process may establish.

              The maximum number of bytes of memory that may  be  locked  into
              RAM.  In effect this limit is rounded down to the nearest multi-
              ple of the system page size.  This limit  affects  mlock(2)  and
              mlockall(2)  and  the mmap(2) MAP_LOCKED operation.  Since Linux
              2.6.9 it also affects the shmctl(2) SHM_LOCK operation, where it
              sets a maximum on the total bytes in shared memory segments (see
              shmget(2)) that may be locked by the real user ID of the calling
              process.   The  shmctl(2) SHM_LOCK locks are accounted for sepa-
              rately  from  the  per-process  memory  locks   established   by
              mlock(2),  mlockall(2),  and  mmap(2)  MAP_LOCKED; a process can
              lock bytes up to this limit in each of these 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.

       RLIMIT_MSGQUEUE (Since Linux 2.6.8)
              Specifies the limit on the number of bytes that can be allocated
              for POSIX message queues for the real user  ID  of  the  calling
              process.   This  limit is enforced for mq_open(3).  Each message
              queue that the user creates counts (until it is removed) against
              this limit according to the formula:

                  bytes = attr.mq_maxmsg * sizeof(

Linux                             2008-10-06                      GETRLIMIT(2)

Scannen Sie den Barcode um die Webseite zu öffnen

Quelle: http://www.trinler.net/de/service/doc/linux/man.html?command=getrlimit
Gedruckt am: 16.12.2017 00:47 GMT+0100 (2017-12-16T00:47:18+01:00)