"rc-service elogind status" says it is stopped, but "ps auxf | grep
elogind" shows elogind-daemon is running. /run/elogind.pid has the
correct pid for the daemon. Based on we searches for similar issues, I
discovered that that /run/openrc/started/elogind did not exist. "ln -s
/etc/init.d/elogind /run/openrc/started/" made rc-service recognize
that the process was actually started.
I can't find anything in /var/log or dmesg about elogind starting. It
is not specified in any runlevel, so I assume it is being started
automatically as needed by something else, although the only other file
in /etc/init.d that needs it is fwupd, which is not currently running
(and not automatically started).
I suppose if I put elogind in the default runlevel, then open-rc will
hopefully start it before it would otherwise get launched, but I'm
curious how I could track down what is currently causing it to be
started.
Jack
- [gentoo-user] problem with open-rc - daemon is running bu... Jack
-