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