summaryrefslogtreecommitdiff
path: root/man/pam_systemd.xml
diff options
context:
space:
mode:
authorPhilip Withnall <withnall@endlessm.com>2019-06-12 09:41:45 +0100
committerZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>2019-10-28 09:44:31 +0100
commitadc09af234047126b5ed65869d575c99dec3f9cc (patch)
treefea2894b0e54370cf7dc0fec474a4214ae1dc983 /man/pam_systemd.xml
parent9ed7de605d7c1a3290e544e92ea5de6141c26bbc (diff)
downloadsystemd-adc09af234047126b5ed65869d575c99dec3f9cc.tar.gz
pam_systemd: Forward systemd.runtime_max_sec setting to session scope
Allow earlier PAM modules to set `systemd.runtime_max_sec`. If they do, parse it and set it as the `RuntimeMaxUSec=` property of the session scope, to limit the maximum lifetime of the session. This could be useful for time-limiting login sessions, for example. Signed-off-by: Philip Withnall <withnall@endlessm.com> Fixes: #12035
Diffstat (limited to 'man/pam_systemd.xml')
-rw-r--r--man/pam_systemd.xml7
1 files changed, 7 insertions, 0 deletions
diff --git a/man/pam_systemd.xml b/man/pam_systemd.xml
index fd8e4fb773..d5be98e4c0 100644
--- a/man/pam_systemd.xml
+++ b/man/pam_systemd.xml
@@ -263,6 +263,12 @@
<listitem><para>Sets unit <varname>IOWeight=</varname>.</para></listitem>
</varlistentry>
+
+ <varlistentry>
+ <term><varname>systemd.runtime_max_sec</varname></term>
+
+ <listitem><para>Sets unit <varname>RuntimeMaxSec=</varname>.</para></listitem>
+ </varlistentry>
</variablelist>
<para>Example data as can be provided from an another PAM module:
@@ -271,6 +277,7 @@ pam_set_data(handle, "systemd.memory_max", (void *)"200M", cleanup);
pam_set_data(handle, "systemd.tasks_max", (void *)"50", cleanup);
pam_set_data(handle, "systemd.cpu_weight", (void *)"100", cleanup);
pam_set_data(handle, "systemd.io_weight", (void *)"340", cleanup);
+pam_set_data(handle, "systemd.runtime_max_sec", (void *)"3600", cleanup);
</programlisting>
</para>