pam_limits (8) - Linux Man Pages
pam_limits: PAM module to limit resources
pam_limits - PAM module to limit resources
- pam_limits.so [conf=/path/to/limits.conf] [debug] [set_all] [utmp_early] [noaudit]
By default limits are taken from the /etc/security/limits.conf config file. Then individual *.conf files from the /etc/security/limits.d/ directory are read. The files are parsed one after another in the order of "C" locale. The effect of the individual files is the same as if all the files were concatenated together in the order of parsing. If a config file is explicitly specified with a module option then the files in the above directory are not parsed.
The module must not be called by a multithreaded application.
- Indicate an alternative limits.conf style configuration file to override the default.
- Print debug information.
- Set the limits for which no value is specified in the configuration file to the one from the process with the PID 1.
- 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.
- Do not report exceeded maximum logins count to the audit subsystem.
MODULE TYPES PROVIDED
- Cannot get current limits.
- No limits found for this user.
- New limits could not be set.
- Cannot read config file.
- Error recovering account name.
- Limits were changed.
- The user is not known to the system.
- Default configuration file
For the services you need resources limits (login for example) put a the following line in /etc/pam.d/login as the last line for that service (usually after the pam_unix session line):
#%PAM-1.0 # # Resource limits imposed on login sessions via pam_limits # session required pam_limits.so
pam_limits was initially written by Cristian Gafton <gafton [at] redhat.com>