Arch Linux

Description:

According to util-linux-2.24/Documentation/PAM-configuration.txt and runuser(1), distributions now need to supply their own PAM configuration files /etc/pam.d/runuser{,-l} .
These files are currently missing in pambase.

Since only root can use `runuser -l <user> ...`, and this command is very useful for starting 'user' sessions from systemd services, (politics aside[1][2]), I would like to strongly suggest using a configuration like

/etc/pam.d/runuser-l:
---------------------
#%PAM-1.0

auth sufficient pam_rootok.so
session include system-login
---

This way, things like media centers, VNC servers and the like can be managed very conveniently using systemd service files.

For example (tested using the example runuser-l configuration file):

/etc/systemd/system/xbmc@.service:
----------------------------------
[Unit]
Description=XBMC on %I
Conflicts=getty@%i.service
After=systemd-user-sessions.service getty@%i.service plymouth-quit.service

[Service]
ExecStart=/usr/bin/runuser -l xbmc -c "/usr/bin/startx /usr/bin/xbmc --standalone"
ExecStop=/usr/bin/runuser -l xbmc -c "/usr/bin/pkill xbmc.bin"
StandardInput=tty
StandardOutput=tty
TTYPath=/dev/%I
Restart=always

[Install]
WantedBy=graphical.target
---

This can be used to start XBMC standalone on any tty:

# systemctl start xbmc@tty2.service

or on system startup (when not using any DM):

# systemctl enable xbmc@tty1

Additional info:
* package version(s)
pambase 20130928-1
util-linux 2.24-1
* config and/or log files etc.


Steps to reproduce: