# phpman > man > PAM_SYSTEMD(8)

[PAM_SYSTEMD(8)](https://www.chedong.com/phpMan.php/man/PAMSYSTEMD/8/markdown)                               pam_systemd                              [PAM_SYSTEMD(8)](https://www.chedong.com/phpMan.php/man/PAMSYSTEMD/8/markdown)



## NAME
       pam_systemd - Register user sessions in the systemd login manager

## SYNOPSIS
       pam_systemd.so

## DESCRIPTION
       **pam**___**systemd** registers user sessions with the systemd login manager [**systemd-logind.service**(8)](https://www.chedong.com/phpMan.php/man/systemd-logind.service/8/markdown),
       and hence the systemd control group hierarchy.

       The module also applies various resource management and runtime parameters to the new
       session, as configured in the **JSON** **User** **Records**[1] of the user, when one is defined.

       On login, this module — in conjunction with systemd-logind.service — ensures the following:

        1. If it does not exist yet, the user runtime directory /run/user/$UID is either created or
           mounted as new "tmpfs" file system with quota applied, and its ownership changed to the
           user that is logging in.

        2. The _$XDG_SESSION_ID_ environment variable is initialized. If auditing is available and
           **pam**___**loginuid.so** was run before this module (which is highly recommended), the variable is
           initialized from the auditing session id (/proc/self/sessionid). Otherwise, an
           independent session counter is used.

        3. A new systemd scope unit is created for the session. If this is the first concurrent
           session of the user, an implicit per-user slice unit below user.slice is automatically
           created and the scope placed into it. An instance of the system service user@.service,
           which runs the systemd user manager instance, is started.

        4. The "$TZ", "$EMAIL" and "$LANG" environment variables are configured for the user, based
           on the respective data from the user's JSON record (if it is defined). Moreover, any
           environment variables explicitly configured in the user record are imported, and the
           umask, nice level, and resource limits initialized.

       On logout, this module ensures the following:

        1. If enabled in [**logind.conf**(5)](https://www.chedong.com/phpMan.php/man/logind.conf/5/markdown) (_KillUserProcesses=_), all processes of the session are
           terminated. If the last concurrent session of a user ends, the user's systemd instance
           will be terminated too, and so will the user's slice unit.

        2. If the last concurrent session of a user ends, the user runtime directory /run/user/$UID
           and all its contents are removed, too.

       If the system was not booted up with systemd as init system, this module does nothing and
       immediately returns **PAM**___**SUCCESS**.

## OPTIONS
       The following options are understood:

       _class=_
           Takes a string argument which sets the session class. The _XDG_SESSION_CLASS_ environment
           variable (see below) takes precedence. One of "user", "greeter", "lock-screen" or
           "background". See **sd**___**session**___**get**___**[class**(3)](https://www.chedong.com/phpMan.php/man/class/3/markdown) for details about the session class.

       _type=_
           Takes a string argument which sets the session type. The _XDG_SESSION_TYPE_ environment
           variable (see below) takes precedence. One of "unspecified", "tty", "x11", "wayland" or
           "mir". See **sd**___**session**___**get**___**[type**(3)](https://www.chedong.com/phpMan.php/man/type/3/markdown) for details about the session type.

       _desktop=_
           Takes a single, short identifier string for the desktop environment. The
           _XDG_SESSION_DESKTOP_ environment variable (see below) takes precedence. This may be used
           to indicate the session desktop used, where this applies and if this information is
           available. For example: "GNOME", or "KDE". It is recommended to use the same identifiers
           and capitalization as for _$XDG_CURRENT_DESKTOP_, as defined by the **Desktop** **Entry**
           **Specification**[2]. (However, note that the option only takes a single item, and not a
           colon-separated list like _$XDG_CURRENT_DESKTOP_.) See **sd**___**session**___**get**___**[desktop**(3)](https://www.chedong.com/phpMan.php/man/desktop/3/markdown) for
           further details.

       _debug_[=]
           Takes an optional boolean argument. If yes or without the argument, the module will log
           debugging information as it operates.

## MODULE TYPES PROVIDED
       Only **session** is provided.

## ENVIRONMENT
       The following environment variables are initialized by the module and available to the
       processes of the user's session:

       _$XDG_SESSION_ID_
           A short session identifier, suitable to be used in filenames. The string itself should be
           considered opaque, although often it is just the audit session ID as reported by
           /proc/self/sessionid. Each ID will be assigned only once during machine uptime. It may
           hence be used to uniquely label files or other resources of this session. Combine this ID
           with the boot identifier, as returned by **sd**___**id128**___**get**___**[boot**(3)](https://www.chedong.com/phpMan.php/man/boot/3/markdown), for a globally unique
           identifier.

       _$XDG_RUNTIME_DIR_
           Path to a user-private user-writable directory that is bound to the user login time on
           the machine. It is automatically created the first time a user logs in and removed on the
           user's final logout. If a user logs in twice at the same time, both sessions will see the
           same _$XDG_RUNTIME_DIR_ and the same contents. If a user logs in once, then logs out again,
           and logs in again, the directory contents will have been lost in between, but
           applications should not rely on this behavior and must be able to deal with stale files.
           To store session-private data in this directory, the user should include the value of
           _$XDG_SESSION_ID_ in the filename. This directory shall be used for runtime file system
           objects such as **AF**___**UNIX** sockets, FIFOs, PID files and similar. It is guaranteed that this
           directory is local and offers the greatest possible file system feature set the operating
           system provides. For further details, see the **XDG** **Base** **Directory** **Specification**[3].
           _$XDG_RUNTIME_DIR_ is not set if the current user is not the original user of the session.

       _$TZ_, _$EMAIL_, _$LANG_
           If a JSON user record is known for the user logging in these variables are initialized
           from the respective data in the record.

       The following environment variables are read by the module and may be used by the PAM service
       to pass metadata to the module. If these variables are not set when the PAM module is invoked
       but can be determined otherwise they are set by the module, so that these variables are
       initialized for the session and applications if known at all.

       _$XDG_SESSION_TYPE_
           The session type. This may be used instead of _type=_ on the module parameter line, and is
           usually preferred.

       _$XDG_SESSION_CLASS_
           The session class. This may be used instead of _class=_ on the module parameter line, and
           is usually preferred.

       _$XDG_SESSION_DESKTOP_
           The desktop identifier. This may be used instead of _desktop=_ on the module parameter
           line, and is usually preferred.

       _$XDG_SEAT_
           The seat name the session shall be registered for, if any.

       _$XDG_VTNR_
           The VT number the session shall be registered for, if any. (Only applies to seats with a
           VT available, such as "seat0")

       If not set, **pam**___**systemd** will initialize _$XDG_SEAT_ and _$XDG_VTNR_ based on the _$DISPLAY_
       variable (if the latter is set).

## SESSION LIMITS
       PAM modules earlier in the stack, that is those that come before **pam**___**systemd.so**, can set
       session scope limits using the PAM context objects. The data for these objects is provided as
       **NUL**-terminated C strings and maps directly to the respective unit resource control
       directives. Note that these limits apply to individual sessions of the user, they do not
       apply to all user processes as a combined whole. In particular, the per-user **user@.service**
       unit instance, which runs the **systemd** **--user** manager process and its children, and is tracked
       outside of any session, being shared by all the user's sessions, is not covered by these
       limits.

       See [**systemd.resource-control**(5)](https://www.chedong.com/phpMan.php/man/systemd.resource-control/5/markdown) for more information about the resources. Also, see
       **pam**___**set**___**[data**(3)](https://www.chedong.com/phpMan.php/man/data/3/markdown) for additional information about how to set the context objects.

       _systemd.memory_max=_
           Sets unit _MemoryMax=_.

       _systemd.tasks_max=_
           Sets unit _TasksMax=_.

       _systemd.cpu_weight=_
           Sets unit _CPUWeight=_.

       _systemd.io_weight=_
           Sets unit _IOWeight=_.

       _systemd.runtime_max_sec=_
           Sets unit _RuntimeMaxSec=_.

       Example data as can be provided from an another PAM module:

           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);



## EXAMPLE
       Here's an example PAM configuration fragment that allows users sessions to be managed by
       systemd-logind.service:

           #%PAM-1.0
           auth      sufficient pam_unix.so
           -auth     sufficient pam_systemd_home.so
           auth      required   pam_deny.so

           account   required   pam_nologin.so
           -account  sufficient pam_systemd_home.so
           account   sufficient pam_unix.so
           account   required   pam_permit.so

           -password sufficient pam_systemd_home.so
           password  sufficient pam_unix.so sha512 shadow try_first_pass use_authtok

           password  required   pam_deny.so

           -session  optional   pam_keyinit.so revoke
           -session  optional   pam_loginuid.so
           -session  optional   pam_systemd_home.so
           **-session**  **optional**   **pam**___**systemd.so**
           session   required   pam_unix.so

## SEE ALSO
       [**systemd**(1)](https://www.chedong.com/phpMan.php/man/systemd/1/markdown), [**systemd-logind.service**(8)](https://www.chedong.com/phpMan.php/man/systemd-logind.service/8/markdown), [**logind.conf**(5)](https://www.chedong.com/phpMan.php/man/logind.conf/5/markdown), [**loginctl**(1)](https://www.chedong.com/phpMan.php/man/loginctl/1/markdown), **pam**___**systemd**___**[home**(8)](https://www.chedong.com/phpMan.php/man/home/8/markdown),
       [**pam.conf**(5)](https://www.chedong.com/phpMan.php/man/pam.conf/5/markdown), [**pam.d**(5)](https://www.chedong.com/phpMan.php/man/pam.d/5/markdown), [**pam**(8)](https://www.chedong.com/phpMan.php/man/pam/8/markdown), **pam**___**[loginuid**(8)](https://www.chedong.com/phpMan.php/man/loginuid/8/markdown), [**systemd.scope**(5)](https://www.chedong.com/phpMan.php/man/systemd.scope/5/markdown), [**systemd.slice**(5)](https://www.chedong.com/phpMan.php/man/systemd.slice/5/markdown),
       [**systemd.service**(5)](https://www.chedong.com/phpMan.php/man/systemd.service/5/markdown)

## NOTES
        1. JSON User Records
           <https://systemd.io/USER_RECORD>

        2. Desktop Entry Specification
           <http://standards.freedesktop.org/desktop-entry-spec/latest/>

        3. XDG Base Directory Specification
           <http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html>



systemd 249                                                                           [PAM_SYSTEMD(8)](https://www.chedong.com/phpMan.php/man/PAMSYSTEMD/8/markdown)
