On Wed, Sep 11, 2013 at 12:39 PM, Zbigniew Jędrzejewski-Szmek <zbys...@kemper.freedesktop.org> wrote: > Makefile.am | 5 +++++ > configure.ac | 7 +++++++ > src/login/pam-module.c | 4 ++-- > src/login/systemd-user | 8 ++++++++ > units/u...@.service.in | 2 +- > 5 files changed, 23 insertions(+), 3 deletions(-) > > New commits: > commit 5c390a4ae0d383b2003074ed011d47876c7e630c > Author: Zbigniew Jędrzejewski-Szmek <zbys...@in.waw.pl> > Date: Wed Sep 11 14:31:14 2013 -0400 > > 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. >
+1 Thanks for doing this - it'll be good for folks implementing user sessions to have a consistent approach. Auke _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
