2011-06-30 04:18:01 +04:00
# This file is part of systemd.
#
# systemd is free software; you can redistribute it and/or modify it
2012-04-12 02:20:58 +04: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-30 04:18:01 +04:00
# (at your option) any later version.
[Unit]
2013-05-09 20:39:15 +04:00
Description=User Manager for %I
2011-06-30 04:18:01 +04:00
After=systemd-user-sessions.service
[Service]
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 22:31:14 +04:00
PAMName=systemd-user
2011-06-30 04:18:01 +04:00
Type=notify
2012-02-08 03:08:10 +04:00
ExecStart=-@rootlibexecdir@/systemd --user
2013-12-27 19:10:36 +04:00
m4_ifdef(`ENABLE_KDBUS',
Environment=DBUS_SESSION_BUS_ADDRESS=kernel:path=/dev/kdbus/%I-user/bus;unix:path=/run/user/%I/bus
,m4_dnl
Environment=DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/%I/bus
)m4_dnl
2013-07-02 03:46:30 +04:00
Slice=user-%i.slice