path: root/modules/pam_limits/limits.conf.5.xml
diff options
Diffstat (limited to 'modules/pam_limits/limits.conf.5.xml')
1 files changed, 11 insertions, 3 deletions
diff --git a/modules/pam_limits/limits.conf.5.xml b/modules/pam_limits/limits.conf.5.xml
index aabcf2cc..a9757a7f 100644
--- a/modules/pam_limits/limits.conf.5.xml
+++ b/modules/pam_limits/limits.conf.5.xml
@@ -230,11 +230,18 @@
- All items support the values <emphasis>-1</emphasis>,
+ All items support the values <emphasis>-1</emphasis>,
<emphasis>unlimited</emphasis> or <emphasis>infinity</emphasis> indicating no limit,
except for <emphasis remap='B'>priority</emphasis> and <emphasis remap='B'>nice</emphasis>.
+ If a hard limit or soft limit of a resource is set to a valid value,
+ but outside of the supported range of the local system, the system
+ may reject the new limit or unexpected behavior may occur. If the
+ control value <emphasis>required</emphasis> is used, the module will
+ reject the login if a limit could not be set.
+ </para>
+ <para>
In general, individual limits have priority over group limits, so if
you impose no limits for <emphasis>admin</emphasis> group, but one of
the members in this group have a limits line, the user will have its
@@ -251,8 +258,8 @@
- after which the rest of the line is ignored.
- The pam_limits module does its best to report configuration problems
- found in its configuration file via <citerefentry>
+ The pam_limits module does report configuration problems
+ found in its configuration file and errors via <citerefentry>
@@ -281,6 +288,7 @@ ftp hard nproc 0
+ <citerefentry><refentrytitle>getrlimit</refentrytitle><manvolnum>3p</manvolnum></citerefentry>