Relevant BUGIDs: 493294

Purpose of commit: bugfix and document

Commit summary:
---------------
The login limit counting seemed to have its math incorrect.
The default has been changed to the sane one, and a new module argument
has been added "utmp_early" that returns the module to its old behavior.

Thanks to Berend De Schouwe for getting to the bottom of this issue.

1 files changed, 9 insertions, 1 deletions

diff --git a/doc/modules/pam_limits.sgml b/doc/modules/pam_limits.sgml
index 961f0b55..eaa16bd9 100644
--- a/doc/modules/pam_limits.sgml
+++ b/doc/modules/pam_limits.sgml
@@ -54,7 +54,8 @@ configuration file discussed below.
 <descrip>
 
 <tag><bf>Recognized arguments:</bf></tag>
-<tt/debug/; <tt>conf=/path/to/file.conf</tt>
+<tt/debug/; <tt>conf=/path/to/file.conf</tt>; <tt>change_uid</tt>;
+<tt>utmp_early</tt>
 
 <tag><bf>Description:</bf></tag>
 
@@ -80,6 +81,13 @@ option if you have problems like login not forking a shell for user
 who has no processes. Be warned that something else may break when
 you do this.
 
+<item><tt/utmp_early/ - 
+some broken applications actually allocate a utmp entry for the user
+before the user is admitted to the system. If some of the services you
+are configuring PAM for do this, you can selectively use this module
+argument to compensate for this behavior and at the same time maintain
+system-wide consistency with a single limits.conf file.
+
 </itemize>
 
 <tag><bf>Examples/suggested usage:</bf></tag>