[systemd-devel] Is masking an error?

[David Timothy Strauss]

On Tue, Jan 21, 2014 at 1:01 AM, Thomas Bächler <thomas at archlinux.org> wrote:
> So, I'd mask systemd-logind.service and remove pam_systemd.so from the
> PAM configuration (I think it's set so that failure is ignored anyway,
> but removing it should still be safer).

It will detect a lack of systemd-logind and no-op, but its detection
method is based on a directory systemd-logind creates on first start
each boot. So, the proper way to disable systemd-logind is to mask it
and either reboot or prune away the directory. Otherwise, pam_systemd
will assume systemd-logind is present *even if it's been stopped*.