1 |
On 2020-10-10 14:02, Jack wrote: |
2 |
> |
3 |
> I suppose if I put elogind in the default runlevel, then open-rc will |
4 |
> hopefully start it before it would otherwise get launched, but I'm |
5 |
> curious how I could track down what is currently causing it to be |
6 |
> started. |
7 |
> |
8 |
|
9 |
If you built elogind with USE=pam, it gets started whenever the first |
10 |
user logs into the machine. Otherwise it can be started if something |
11 |
calls it over dbus. IIRC the usual advice is to place the OpenRC service |
12 |
in the "boot" runlevel to ensure that OpenRC is the one to start it (and |
13 |
that e.g. rc-status will have the correct information). |