Published at LXer:
David Herrmann is on a coding spree this summer. His latest set of ten patches this week provide for device management support using systemd's logind service...
after a fresh install and reboot, the bootmessage on tty1 says:failed to load loginmanager see 'systemctl status systemd-logind.service' for detailssystemd-logind.service - Login Service
Loaded: loaded (/usr/lib/systemd/system/systemd-logind.service; static)
Active: active (running) since So 2014-08-03 21:56:21 CEST; 2min 26s ago
Thanks for your time, Wonderwoofy & brain0. Ultimately I think I was confused and misled by the news item's title using the name 'logind' instead of 'systemd-logind' or just 'systemd'. I thought I was dealing with something that was distinct from, yet somewhat dependent on, systemd.
htop shows /usr/lib/systemd/systemd-logind is the one to blameI need to perform systemctl stop systemd-logind to resolve thisand from time to time NM-applet complains about device not managablesystemctl restart NetworkManager solve this small issue
systemd, a system and service manager for Linux, compatible with SysV and LSB init scripts, that provides aggressive parallelization capabilities and uses socket and D-Bus activation for starting services, is now at version 208.
A lot of new features have been updated in the previous versions of system, and this latest iteration isn't any different.
bwat47 wrote:Make sure all the lid/button handling stuff is disabled in /etc/systemd/logind.confI have the logind.conf at default which according to the comment seems to mean OFF. I notice that even when acpid is working properly the event is passed to logind (according to journalctl -f).David Batson wrote:Maybe: https://wiki.archlinux.org/index.php/Sy … arly_start ? I'll give that a try.