From: Zbigniew Jędrzejewski-Szmek Date: Wed, 28 May 2025 13:23:48 +0000 (+0200) Subject: man/pam_systemd: use consistently X-Git-Tag: v258-rc1~460^2~6 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=3a23e96b6799589caef547306f5f85f1feaf73dd;p=thirdparty%2Fsystemd.git man/pam_systemd: use consistently For some reason, and were used interchangeably. --- diff --git a/man/pam_systemd.xml b/man/pam_systemd.xml index c488e5bec4b..b29bf615965 100644 --- a/man/pam_systemd.xml +++ b/man/pam_systemd.xml @@ -113,7 +113,7 @@ user-early - Similar to user but sessions of this class are not ordered after systemd-user-sessions.service8, i.e. may be started before regular sessions are allowed to be established. This session class is the default for sessions of the root user that would otherwise qualify for the user class, see above. (Added in v256.) + Similar to user but sessions of this class are not ordered after systemd-user-sessions.service8, i.e. may be started before regular sessions are allowed to be established. This session class is the default for sessions of the root user that would otherwise qualify for the user class, see above. (Added in v256.) user-light @@ -125,15 +125,15 @@ user-incomplete - Similar to user but for sessions which are not fully set up yet, i.e. have no home directory mounted or similar. This is used by systemd-homed.service8 to allow users to log in via ssh1 before their home directory is mounted, delaying the mount until the user provided the unlock password. Sessions of this class are upgraded to the regular user class once the home directory is activated. + Similar to user but for sessions which are not fully set up yet, i.e. have no home directory mounted or similar. This is used by systemd-homed.service8 to allow users to log in via ssh1 before their home directory is mounted, delaying the mount until the user provided the unlock password. Sessions of this class are upgraded to the regular user class once the home directory is activated. greeter - Similar to user but for sessions that are spawned by a display manager ephemerally and which prompt the user for login credentials. + Similar to user but for sessions that are spawned by a display manager ephemerally and which prompt the user for login credentials. lock-screen - Similar to user but for sessions that are spawned by a display manager ephemerally and which show a lock screen that can be used to unlock locked user accounts or sessions. + Similar to user but for sessions that are spawned by a display manager ephemerally and which show a lock screen that can be used to unlock locked user accounts or sessions. background @@ -166,9 +166,9 @@ 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, mir, or - web. See + environment variable (see below) takes precedence. One of unspecified, + tty, x11, wayland, mir, or + web. See sd_session_get_type3 for details about the session type. @@ -181,7 +181,7 @@ 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 + 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. (However, note that the option only takes a single item, and not a colon-separated list @@ -229,16 +229,16 @@ default-capability-bounding-set= default-capability-ambient-set= - Takes a comma-separated list of process capabilities - (e.g. CAP_WAKE_ALARM, CAP_BLOCK_SUSPEND, …) to set for the + Takes a comma-separated list of process capabilities (e.g. + CAP_WAKE_ALARM, CAP_BLOCK_SUSPEND, …) to set for the invoked session's processes, if the user record does not encode appropriate sets of capabilities directly. See capabilities7 for details on the capabilities concept. If not specified, the default bounding set is left as is (i.e. usually contains the full set of capabilities). The default ambient set is set to CAP_WAKE_ALARM for regular users if the PAM session is associated with a local - seat or if it is invoked for the systemd-user service. Otherwise, defaults to the - empty set. + seat or if it is invoked for the systemd user service user@.service. Otherwise, + defaults to the empty set.