On 2020.10.10 17:30, Michael Orlitzky wrote:
On 2020-10-10 14:02, Jack wrote:
>
> 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.
>
If you built elogind with USE=pam, it gets started whenever the first
user logs into the machine. Otherwise it can be started if something
calls it over dbus. IIRC the usual advice is to place the OpenRC
service
in the "boot" runlevel to ensure that OpenRC is the one to start it
(and
that e.g. rc-status will have the correct information).
Thanks. It looks like the pam USE flag is the culprit here. I've
added elogind to boot runlevel.
Jack
