diff options
| author | Lennart Poettering <lennart@poettering.net> | 2016-05-04 18:57:15 +0200 |
|---|---|---|
| committer | Lennart Poettering <lennart@poettering.net> | 2016-05-05 22:50:09 +0200 |
| commit | 183e0738427b83667512276a3e8c10274c0824cc (patch) | |
| tree | cc0267b812b7b5d70694468cc25e51c96c588880 /man | |
| parent | 37818090c99871577c0cfd8171901eb7e2050be9 (diff) | |
logind: enforce a limit on current user sessions
We really should put limits on all resources we manage, hence add one to the
number of concurrent sessions, too. This was previously unbounded, hence set a
relatively high limit of 8K by default.
Note that most PAM setups will actually invoke pam_systemd prefixed with "-",
so that the return code of pam_systemd is ignored, and the login attempt
succeeds anyway. On systems like this the session will be created but is not
tracked by systemd.
Diffstat (limited to 'man')
| -rw-r--r-- | man/logind.conf.xml | 9 |
1 files changed, 9 insertions, 0 deletions
diff --git a/man/logind.conf.xml b/man/logind.conf.xml index 6ba35414be..405dcf9041 100644 --- a/man/logind.conf.xml +++ b/man/logind.conf.xml @@ -297,6 +297,15 @@ </varlistentry> <varlistentry> + <term><varname>SessionsMax=</varname></term> + + <listitem><para>Controls the maximum number of concurrent user sessions to manage. Defaults to 8192 + (8K). Depending on how the <filename>pam_systemd.so</filename> module is included in the PAM stack + configuration, further login sessions will either be refused, or permitted but not tracked by + <filename>systemd-logind</filename>.</para></listitem> + </varlistentry> + + <varlistentry> <term><varname>UserTasksMax=</varname></term> <listitem><para>Sets the maximum number of OS tasks each user |