slackwares virus at work
by Ressy from LinuxQuestions.org on (#5PYCJ)
The virus systemd (its slackware elogind variant) as of some updates recently, is causing long delays in logging into console.
ssh logins are instant however.
This is headless system with no bloatware, errr I mean GUI crud
Sep 24 20:58:19 fx login: pam_unix(login:session): session opened for user root(uid=0) by LOGIN(uid=0)
Sep 24 20:58:19 fx elogind[24285]: elogind is already running as PID 1275
(at this point enter was hit on password, then)
Sep 24 20:58:44 fx dbus-daemon[1260]: [system] Failed to activate service 'org.freedesktop.login1': timed out (service_start_timeout=25000ms)
Sep 24 20:58:44 fx login: pam_elogind(login:session): Failed to create session: Failed to activate service 'org.freedesktop.login1': timed out (service_start_timeout=25000ms)
Sep 24 20:58:44 fx login: ROOT LOGIN ON tty1
Two evil viruses systemd and pam working together to destroy our slackware experiences.
I swear systemd was written by Billy, formerly of Redmond.
The following is what is common reports elsewhere
However, it looked like dbus-daemon had restarted at some point and systemd-logind had not been restarted since then
I note however this is upon a reboot, and every susbsequent access.
Edited: restarting elogind seems to resolve it at this stage.
ssh logins are instant however.
This is headless system with no bloatware, errr I mean GUI crud
Sep 24 20:58:19 fx login: pam_unix(login:session): session opened for user root(uid=0) by LOGIN(uid=0)
Sep 24 20:58:19 fx elogind[24285]: elogind is already running as PID 1275
(at this point enter was hit on password, then)
Sep 24 20:58:44 fx dbus-daemon[1260]: [system] Failed to activate service 'org.freedesktop.login1': timed out (service_start_timeout=25000ms)
Sep 24 20:58:44 fx login: pam_elogind(login:session): Failed to create session: Failed to activate service 'org.freedesktop.login1': timed out (service_start_timeout=25000ms)
Sep 24 20:58:44 fx login: ROOT LOGIN ON tty1
Two evil viruses systemd and pam working together to destroy our slackware experiences.
I swear systemd was written by Billy, formerly of Redmond.
The following is what is common reports elsewhere
However, it looked like dbus-daemon had restarted at some point and systemd-logind had not been restarted since then
I note however this is upon a reboot, and every susbsequent access.
Edited: restarting elogind seems to resolve it at this stage.