[systemd-devel] Upgrade 232 -> 233: user at XXX.service: Failed at step PAM spawning...

[Mantas Mikulėnas]

Linux-PAM supports -prefix everywhere, but it simply means "ignore
nonexistent modules instead of warning". (Therefore it doesn't make sense
on distros where pam_systemd is guaranteed to exist.)

However, the dash prefix never ignores errors returned by the module itself
– that's what the 'optional' field is for.

On Sat, Apr 29, 2017, 14:30 Lennart Poettering <lennart at poettering.net>
wrote:

> On Sat, 29.04.17 13:25, Vlad (vovan at vovan.nl) wrote:
>
> > Lennart,
> >
> > I've just tried your suggestion as well, but it doesn't change behavior.
> > I'm just wondering how it would be possible to investigate the error.
> > The message "user at xxx.service: Failed at step PAM spawning
> > /usr/lib/systemd/systemd: Operation not permitted" isn't very
> > descriptive. I enabled debug for pam_systemd, but it doesn't give useful
> > information in my case.
>
> Well, I figure you should look for PAM level debugging, not
> systemd level debugging for this. Contact the PAM community for help
> on that.
>
> But do note again that distros vary greatly on PAM, and while "-" is
> typically used on Fedora-based distros, IIRC other distros don't know
> or use that concept. Please ask your distro for help.
>
> Lennart
>
> --
> Lennart Poettering, Red Hat
> _______________________________________________
> systemd-devel mailing list
> systemd-devel at lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/systemd-devel
>
-- 

Mantas Mikulėnas <grawity at gmail.com>
Sent from my phone
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/systemd-devel/attachments/20170429/d0725b44/attachment.html>