diff options
author | Lennart Poettering <lennart@poettering.net> | 2016-12-29 10:55:27 +0100 |
---|---|---|
committer | Martin Pitt <martin.pitt@ubuntu.com> | 2016-12-29 10:55:27 +0100 |
commit | 9eb484fa40856a5f4d17b1c7dfe414a727758a89 (patch) | |
tree | bc836fc04501459cb0111fe4326ac866e89805f8 /man | |
parent | Merge pull request #4989 from poettering/nss-einval (diff) | |
download | systemd-9eb484fa40856a5f4d17b1c7dfe414a727758a89.tar.xz systemd-9eb484fa40856a5f4d17b1c7dfe414a727758a89.zip |
man: add brief documentation for the (sd-pam) processes created due to PAMName= (#4967)
A follow-up for #4942, adding a brief but more correct explanation of
the processes.
Diffstat (limited to 'man')
-rw-r--r-- | man/systemd.exec.xml | 19 |
1 files changed, 11 insertions, 8 deletions
diff --git a/man/systemd.exec.xml b/man/systemd.exec.xml index 812e615530..2dd8107684 100644 --- a/man/systemd.exec.xml +++ b/man/systemd.exec.xml @@ -859,14 +859,17 @@ <varlistentry> <term><varname>PAMName=</varname></term> - <listitem><para>Sets the PAM service name to set up a session - as. If set, the executed process will be registered as a PAM - session under the specified service name. This is only useful - in conjunction with the <varname>User=</varname> setting. If - not set, no PAM session will be opened for the executed - processes. See - <citerefentry project='man-pages'><refentrytitle>pam</refentrytitle><manvolnum>8</manvolnum></citerefentry> - for details.</para></listitem> + <listitem><para>Sets the PAM service name to set up a session as. If set, the executed process will be + registered as a PAM session under the specified service name. This is only useful in conjunction with the + <varname>User=</varname> setting, and is otherwise ignored. If not set, no PAM session will be opened for the + executed processes. See <citerefentry + project='man-pages'><refentrytitle>pam</refentrytitle><manvolnum>8</manvolnum></citerefentry> for + details.</para> + + <para>Note that for each unit making use of this option a PAM session handler process will be maintained as + part of the unit and stays around as long as the unit is active, to ensure that appropriate actions can be + taken when the unit and hence the PAM session terminates. This process is named <literal>(sd-pam)</literal> and + is an immediate child process of the unit's main process.</para></listitem> </varlistentry> <varlistentry> |