[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#27580: Elogin doesn't start properly

From: Ludovic Courtès
Subject: bug#27580: Elogin doesn't start properly
Date: Tue, 11 Jul 2017 00:21:37 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/25.2 (gnu/linux)


William <address@hidden> skribis:

> Elogind only starts when loginctl is executed as loginctl activates
> elogind via DBus, meaning that it doesn't record any logins before
> loginctl is run. I don't believe that this is intended; my Arch Linux
> install doesn't miss any logins.

I thought pam_elogind would trigger bus-activation but it does not,
because of this:

        /* Make this a NOP on non-logind systems */
        if (!logind_running())
                return PAM_SUCCESS;


  static inline bool logind_running(void) {
          return access("/run/systemd/seats/", F_OK) >= 0;

When the system is started, /run/systemd is empty, so pam_elogind
directly returns success.

I’m looking for a way to work around this; to be continued…


PS: The problem does not happen with X and SLiM because they somehow
    activate elogind before one has logged in.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]