From 97c26c1924b076ef23ebe4381558e8aa025712b2 Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Sun, 7 Apr 2024 16:54:37 +0200 Subject: Adding upstream version 1:4.13+dfsg1. Signed-off-by: Daniel Baumann --- man/limits.5.xml | 195 +++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 195 insertions(+) create mode 100644 man/limits.5.xml (limited to 'man/limits.5.xml') diff --git a/man/limits.5.xml b/man/limits.5.xml new file mode 100644 index 0000000..0b459bc --- /dev/null +++ b/man/limits.5.xml @@ -0,0 +1,195 @@ + + + +]> + + + + + Luca + Berra + Creation, 1997 + + + Thomas + Kłoczko + kloczek@pld.org.pl + shadow-utils maintainer, 2000 - 2007 + + + Nicolas + François + nicolas.francois@centraliens.net + shadow-utils maintainer, 2007 - now + + + + limits + 5 + File Formats and Configuration Files + shadow-utils + &SHADOW_UTILS_VERSION; + + + limits + resource limits definition + + + + + DESCRIPTION + + The limits file + (/etc/limits by default + or LIMITS_FILE defined config.h) describes + the resource limits you wish to impose. It should be owned by + root and readable by root account only. + + + + By default no quota is imposed on 'root'. In fact, there is no way to + impose limits via this procedure to root-equiv accounts (accounts with + UID 0). + + + Each line describes a limit for a user in the form: + + + user LIMITS_STRING + + + or in the form: + + + @group LIMITS_STRING + + + + The LIMITS_STRING is a string of a concatenated + list of resource limits. Each limit consists of a letter identifier + followed by a numerical limit. + + + The valid identifiers are: + + + A: max address space (KB) + C: max core file size (KB) + D: max data size (KB) + F: maximum file size (KB) + K: file creation mask, set by + + umask2 + . + + I: max nice value (0..39 which translates to + 20..-19) + L: max number of logins for this user + M: max locked-in-memory address space (KB) + N: max number of open files + O: max real time priority + P: process priority, set by + + setpriority2 + . + + R: max resident set size (KB) + S: max stack size (KB) + T: max CPU time (MIN) + U: max number of processes + + + + For example, L2D2048N5 is a valid + LIMITS_STRING. For reading convenience, the + following entries are equivalent: + + + + username L2D2048N5 + username L2 D2048 N5 + + + + Be aware that after username the rest + of the line is considered a limit string, thus comments are not + allowed. An invalid limits string will be rejected (not considered) by + the login program. + + + + The default entry is denoted by username "*". If + you have multiple default entries in + your LIMITS_FILE, then the last one will be used + as the default entry. + + + + The limits specified in the form "@group" + apply to the members of the specified + group. + + + + If more than one line with limits for a user exist, only the first line for + this user will be considered. + + + + If no lines are specified for a user, the last + @group line matching a group whose the + user is a member of will be considered, or the last line with + default limits if no groups contain the user. + + + + To completely disable limits for a user, a single dash + "-" will do. + + + + To disable a limit for a user, a single dash + "-" can be used instead of the numerical + value for this limit. + + + + Also, please note that all limit settings are set PER LOGIN. They are + not global, nor are they permanent. Perhaps global limits will come, + but for now this will have to do ;) + + + + + FILES + + + /etc/limits + + + + + + + SEE ALSO + + + login1 + , + + setpriority2 + , + + setrlimit2 + . + + + -- cgit v1.2.3