2011-06-29 17:18:01 -07:00
|
|
|
# This file is part of systemd.
|
|
|
|
#
|
|
|
|
# systemd is free software; you can redistribute it and/or modify it
|
2012-04-11 15:20:58 -07:00
|
|
|
# under the terms of the GNU Lesser General Public License as published by
|
|
|
|
# the Free Software Foundation; either version 2.1 of the License, or
|
2011-06-29 17:18:01 -07:00
|
|
|
# (at your option) any later version.
|
|
|
|
|
|
|
|
[Unit]
|
2014-01-08 14:20:45 -08:00
|
|
|
Description=User Manager for UID %i
|
2011-06-29 17:18:01 -07:00
|
|
|
After=systemd-user-sessions.service
|
|
|
|
|
|
|
|
[Service]
|
2014-01-05 20:00:16 -08:00
|
|
|
User=%i
|
Add pam configuration to allow user sessions to work out of the box
systemd-logind will start user@.service. user@.service unit uses
PAM with service name 'systemd-user' to perform account and session
managment tasks. Previously, the name was 'systemd-shared', it is
now changed to 'systemd-user'.
Most PAM installations use one common setup for different callers.
Based on a quick poll, distributions fall into two camps: those that
have system-auth (Redhat, Fedora, CentOS, Arch, Gentoo, Mageia,
Mandriva), and those that have common-auth (Debian, Ubuntu, OpenSUSE).
Distributions that have system-auth have just one configuration file
that contains auth, password, account, and session blocks, and
distributions that have common-auth also have common-session,
common-password, and common-account. It is thus impossible to use one
configuration file which would work for everybody. systemd-user now
refers to system-auth, because it seems that the approach with one
file is more popular and also easier, so let's follow that.
2013-09-11 11:31:14 -07:00
|
|
|
PAMName=systemd-user
|
2011-06-29 17:18:01 -07:00
|
|
|
Type=notify
|
2012-02-07 15:08:10 -08:00
|
|
|
ExecStart=-@rootlibexecdir@/systemd --user
|
2013-07-01 16:46:30 -07:00
|
|
|
Slice=user-%i.slice
|