Hallo, dies ist ein Test.

PWD: /www/data-lst1/unixsoft/unixsoft/kaempfer/.public_html

Running in File Mode
Relative path: ./../../../../../data-stud/../../usr/man/man2/getrlimit.2
Real path: /usr/share/man/man2/getrlimit.2
Zurück

'\" te
.\" Copyright (c) 1989, AT&T. All rights reserved.
.\" Copyright (c) 1994, The X/Open Company Ltd. All rights reserved.
.\" Portions Copyright (c) 2006, 2023, Oracle and/or its affiliates.
.\" Oracle gratefully acknowledges The Open Group for permission to reproduce portions of its copyrighted documentation. Original documentation from The Open Group can be obtained online at http://www.opengroup.org/bookstore/.
.\" The Institute of Electrical and Electronics Engineers and The Open Group, have given us permission to reprint portions of their documentation. In the following statement, the phrase "this text" refers to portions of the system documentation. Portions of this text are reprinted and reproduced in electronic form in the Sun OS Reference Manual, from IEEE Std 1003.1, 2004 Edition, Standard for Information Technology -- Portable Operating System Interface (POSIX), The Open Group Base Specifications Issue 6, Copyright (C) 2001-2004 by the Institute of Electrical and Electronics Engineers, Inc and The Open Group. In the event of any discrepancy between these versions and the original IEEE and The Open Group Standard, the original IEEE and The Open Group Standard is the referee document. The original Standard can be obtained online at http://www.opengroup.org/unix/online.html. This notice shall appear on any product containing this material.
.TH getrlimit 2 "30 Jan 2023" "Oracle Solaris 11.4" "System Calls"
.SH NAME
getrlimit, setrlimit \- control maximum system resource consumption
.SH SYNOPSIS

.LP
.nf
#include <sys/resource.h>

\fBint\fR \fBgetrlimit\fR(\fBint\fR \fIresource\fR, \fBstruct rlimit *\fR\fIrlp\fR);
.fi

.LP
.nf
\fBint\fR \fBsetrlimit\fR(\fBint\fR \fIresource\fR, \fBconst struct rlimit *\fR\fIrlp\fR);
.fi
.SH DESCRIPTION
.sp
.LP
Limits on the consumption of a variety of system resources by a process and each process it creates may be obtained with the \fBgetrlimit()\fR and set with \fBsetrlimit()\fR functions.
.sp
.LP
Each call to either \fBgetrlimit()\fR or \fBsetrlimit()\fR identifies a specific resource to be operated upon as well as a resource limit. A resource limit is a pair of values: one specifying the current (soft) limit, the other a maximum (hard) limit. Soft limits may be changed by a process to any value that is less than or equal to the hard limit. A process may (irreversibly) lower its hard limit to any value that is greater than or equal to the soft limit. Only a process with {\fBPRIV_SYS_RESOURCE\fR} asserted in the effective set can raise a hard limit. Both hard and soft limits can be changed in a single call to \fBsetrlimit()\fR subject to the constraints described above. Limits may have an "infinite" value of \fBRLIM_INFINITY\fR. The \fIrlp\fR argument is a pointer to a \fBstruct rlimit\fR that includes the following members:
.sp
.in +2
.nf
rlim_t    rlim_cur;     /* current (soft) limit */
rlim_t    rlim_max;     /* hard limit */
.fi
.in -2
.sp
.sp
.LP
The type \fBrlim_t\fR is an arithmetic data type to which objects of type \fBint\fR, \fBsize_t\fR, and \fBoff_t\fR can be cast without loss of information.
.sp
.LP
The possible resources, their descriptions, and the actions taken when the current limit is exceeded are summarized as follows:
.sp
.ne 2
.mk
.na
\fB\fBRLIMIT_AS\fR\fR
.ad
.RS 17n
.rt
The maximum size, in bytes, of the address space mapped by a process. If this limit is exceeded, the \fBbrk\fR(2), \fBmalloc\fR(3C), \fBmmap\fR(2) and \fBsbrk\fR(2) functions will fail with \fBerrno\fR set to \fBENOMEM\fR. In addition, the automatic stack growth will fail with the effects outlined above.
.RE

.sp
.ne 2
.mk
.na
\fB\fBRLIMIT_CORE\fR\fR
.ad
.RS 17n
.rt
The maximum size of a core file in bytes that may be created by a process. A limit of \fB0\fR will prevent the creation of a core file. The writing of a core file will terminate at this size.
.RE

.sp
.ne 2
.mk
.na
\fB\fBRLIMIT_CPU\fR\fR
.ad
.RS 17n
.rt
The maximum amount of CPU time in seconds used by a process. This is a soft limit only. The \fBSIGXCPU\fR signal is sent to the process. If the process is holding or ignoring \fBSIGXCPU\fR, the behavior is scheduling class defined.
.RE

.sp
.ne 2
.mk
.na
\fB\fBRLIMIT_DATA\fR\fR
.ad
.RS 17n
.rt
The maximum size of a process's heap in bytes. The \fBbrk\fR(2) function will fail with \fBerrno\fR set to \fBENOMEM\fR.
.RE

.sp
.ne 2
.mk
.na
\fB\fBRLIMIT_FSIZE\fR\fR
.ad
.RS 17n
.rt
The maximum size of a file in bytes that may be created by a process. A limit of \fB0\fR will prevent the creation of a file. The \fBSIGXFSZ\fR signal is sent to the process. If the process is holding or ignoring \fBSIGXFSZ\fR, continued attempts to increase the size of a file beyond the limit will fail with \fBerrno\fR set to \fBEFBIG\fR.
.RE

.sp
.ne 2
.mk
.na
\fB\fBRLIMIT_NOFILE\fR\fR
.ad
.RS 17n
.rt
One more than the maximum value that the system may assign to a newly created descriptor. This limit constrains the number of file descriptors that a process may create. If a process already has the maximum number of file descriptors open, attempts to open more will fail with \fBerrno\fR set to \fBEMFILE\fR.
.RE

.sp
.ne 2
.mk
.na
\fB\fBRLIMIT_STACK\fR\fR
.ad
.RS 17n
.rt
The maximum size of a process's main thread stack in bytes. The system will not automatically grow the stack beyond this limit.
.sp
Within a process, \fBsetrlimit()\fR will increase the limit on the size of your stack, but will not move current memory segments to allow for that growth. To guarantee that the process stack can grow to the limit, the limit must be altered prior to the execution of the process in which the new stack size is to be used.
.sp
Within a multithreaded process, \fBsetrlimit()\fR has no impact on the stack size limit for the calling thread if the calling thread is not the main thread. A call to \fBsetrlimit()\fR for \fBRLIMIT_STACK\fR impacts only the main thread's stack, and should be made only from the main thread, if at all.
.sp
The \fBSIGSEGV\fR signal is sent to the process. If the process is holding or ignoring \fBSIGSEGV\fR, or is catching \fBSIGSEGV\fR and has not made arrangements to use an alternate stack (see \fBsigaltstack\fR(2)), the disposition of \fBSIGSEGV\fR will be set to \fBSIG_DFL\fR before it is sent.
.RE

.sp
.ne 2
.mk
.na
\fB\fBRLIMIT_VMEM\fR\fR
.ad
.RS 17n
.rt
This is an alternate name for \fBRLIMIT_AS\fR. Portable software should prefer the standard \fBRLIMIT_AS\fR over this non-standardized name.
.RE

.sp
.LP
Because limit information is stored in the per-process information, the shell builtin \fBulimit\fR command must directly execute this system call if it is to affect all future processes created by the shell.
.sp
.LP
The value of the current limit of the following resources affect these implementation defined parameters:
.sp
.TS
tab(
);
cw(2.75i) lw(2.75i) 
lw(2.75i) lw(2.75i) 
.
Limit
Implementation Defined Constant
\fBRLIMIT_FSIZE\fR
\fBFCHR_MAX\fR
\fBRLIMIT_NOFILE\fR
\fBOPEN_MAX\fR
.TE
.sp
.sp
.LP
When using the \fBgetrlimit()\fR function, if a resource limit can be represented correctly in an object of type \fBrlim_t\fR, then its representation is returned; otherwise, if the value of the resource limit is equal to that of the corresponding saved hard limit, the value returned is \fBRLIM_SAVED_MAX\fR; otherwise the value returned is \fBRLIM_SAVED_CUR\fR.
.sp
.LP
When using the \fBsetrlimit()\fR function, if the requested new limit is \fBRLIM_INFINITY\fR, the new limit will be "no limit"; otherwise if the requested new limit is \fBRLIM_SAVED_MAX\fR, the new limit will be the corresponding saved hard limit; otherwise, if the requested new limit is \fBRLIM_SAVED_CUR\fR, the new limit will be the corresponding saved soft limit; otherwise, the new limit will be the requested value. In addition, if the corresponding saved limit can be represented correctly in an object of type \fBrlim_t\fR, then it will be overwritten with the new limit.
.sp
.LP
The result of setting a limit to \fBRLIM_SAVED_MAX\fR or \fBRLIM_SAVED_CUR\fR is unspecified unless a previous call to \fBgetrlimit()\fR returned that value as the soft or hard limit for the corresponding resource limit.
.sp
.LP
A limit whose value is greater than \fBRLIM_INFINITY\fR is permitted.
.sp
.LP
The \fBexec\fR family of functions also cause resource limits to be saved. See \fBexec\fR(2).
.SH RETURN VALUES
.sp
.LP
Upon successful completion, \fBgetrlimit()\fR and \fBsetrlimit()\fR return \fB0\fR. Otherwise, these functions return \fB\(mi1\fR and set \fBerrno\fR to indicate the error.
.SH ERRORS
.sp
.LP
The \fBgetrlimit()\fR and \fBsetrlimit()\fR functions will fail if:
.sp
.ne 2
.mk
.na
\fB\fBEFAULT\fR\fR
.ad
.RS 10n
.rt
The \fIrlp\fR argument points to an illegal address.
.RE

.sp
.ne 2
.mk
.na
\fB\fBEINVAL\fR\fR
.ad
.RS 10n
.rt
An invalid \fIresource\fR was specified; or in a \fBsetrlimit()\fR call, the new \fBrlim_cur\fR exceeds the new \fBrlim_max\fR.
.RE

.sp
.ne 2
.mk
.na
\fB\fBEPERM\fR\fR
.ad
.RS 10n
.rt
The limit specified to \fBsetrlimit()\fR would have raised the maximum limit value and {\fBPRIV_SYS_RESOURCE\fR} is not asserted in the effective set of the current process.
.RE

.sp
.LP
The \fBsetrlimit()\fR function may fail if:
.sp
.ne 2
.mk
.na
\fB\fBEINVAL\fR\fR
.ad
.RS 10n
.rt
The limit specified cannot be lowered because current usage is already higher than the limit.
.RE

.SH USAGE
.sp
.LP
The \fBgetrlimit()\fR and \fBsetrlimit()\fR functions have transitional interfaces for 64-bit file offsets. See \fBlf64\fR(7).
.sp
.LP
The \fBrlimit\fR functionality is now provided by the more general resource control facility described on the \fBsetrctl\fR(2) manual page. The actions associated with the resource limits described above are true at system boot, but an administrator can modify the local configuration to modify signal delivery or type. Application authors that utilize rlimits for the purposes of resource awareness should investigate the resource controls facility.
.sp
.LP
The following table lists the \fBrlimit\fR to \fBrctl\fR mapping:
.sp
.TS
tab(
) box;
cw(2.75i) |cw(2.75i) 
lw(2.75i) |lw(2.75i) 
.
\fBrlimit\fR
\fBrctl\fR
_
\fBRLIMIT_AS\fR
\fBprocess.max-address-space\fR
_
\fBRLIMIT_CORE\fR
\fBprocess.max-core-size\fR
_
\fBRLIMIT_CPU\fR
\fBprocess.max-cpu-time\fR
_
\fBRLIMIT_DATA\fR
\fBprocess.max-data-size\fR
_
\fBRLIMIT_FSIZE\fR
\fBprocess.max-file-size\fR
_
\fBRLIMIT_NOFILE\fR
\fBprocess.max-file-descriptor\fR
_
\fBRLIMIT_STACK\fR
\fBprocess.max-stack-size\fR
.TE
.sp
.sp
.LP
A variety of additional limits are available via the \fBgetrctl()\fR and \fBsetrctl()\fR functions. For more information, see \fBresource-controls\fR(7).
.SH ATTRIBUTES
.sp
.LP
See \fBattributes\fR(7) for descriptions of the following attributes:
.sp
.TS
tab(
) box;
cw(2.75i) |cw(2.75i) 
lw(2.75i) |lw(2.75i) 
.
ATTRIBUTE TYPE
ATTRIBUTE VALUE
_
Interface Stability
Committed
_
Standard
See \fBstandards\fR(7).
.TE
.sp
.SH SEE ALSO
.sp
.LP
\fBulimit\fR(1), \fBbrk\fR(2), \fBexec\fR(2), \fBfork\fR(2), \fBopen\fR(2), \fBsetrctl\fR(2), \fBsigaltstack\fR(2), \fBgetdtablesize\fR(3C), \fBmalloc\fR(3C), \fBsignal\fR(3C), \fBsysconf\fR(3C), \fBsignal.h\fR(3HEAD), \fBattributes\fR(7), \fBlf64\fR(7), \fBprivileges\fR(7), \fBresource-controls\fR(7), \fBstandards\fR(7), \fBrctladm\fR(8)
.sp
.LP
\fIOracle Solaris 11.4 Tunable Parameters Reference Manual\fR
.SH HISTORY
.sp
.LP
The \fBgetrlimit()\fR and \fBsetrlimit()\fR functions have been included in all Sun and Oracle releases of Solaris.
.sp
.LP
Support for the following \fIresource\fR values is available in Oracle Solaris starting with the listed release:
.sp
.TS
tab(
) box;
cw(4.71i) |cw(0.79i) 
lw(4.71i) |lw(0.79i) 
.
RESOURCE
RELEASE
_
\fBRLIMIT_AS\fR, \%\fBRLIMIT_VMEM\fR
2.0
_
T{
\fBRLIMIT_CORE\fR, \%\fBRLIMIT_CPU\fR, \%\fBRLIMIT_DATA\fR, \%\fBRLIMIT_FSIZE\fR, \%\fBRLIMIT_NOFILE\fR, \%\fBRLIMIT_STACK\fR
T}
1.0
.TE
.sp