| 1 |
On Tue, 29 Oct 2019 23:03:15 +0000 |
| 2 |
James Le Cuirot <chewi@g.o> wrote: |
| 3 |
|
| 4 |
> On Tue, 29 Oct 2019 11:23:20 -0700 |
| 5 |
> Patrick McLean <chutzpah@g.o> wrote: |
| 6 |
> |
| 7 |
> > On Tue, 29 Oct 2019 16:10:37 +0100 |
| 8 |
> > Andreas Sturmlechner <asturm@g.o> wrote: |
| 9 |
> > |
| 10 |
> > > |
| 11 |
> > > Anyone else who thinks this should not be restricted to just |
| 12 |
> > > desktop profiles? |
| 13 |
> > |
| 14 |
> > I am not aware of any use cases for elogind/consolekit on servers, |
| 15 |
> > it's really for machines where you have to distinguish between |
| 16 |
> > someone connecting remotely and someone physically using a |
| 17 |
> > keyboard/mouse connected to the machine. |
| 18 |
> |
| 19 |
> I switched from consolekit to elogind on my normally headless ARM box. |
| 20 |
> It runs XMMS2 and outputs through PulseAudio. Under consolekit, my |
| 21 |
> user's /var/run directory would disappear after a while, taking the |
| 22 |
> pulse socket with it. Under elogind, I was able to set my user to |
| 23 |
> "linger", which fixed the issue. It's not a typical use case but yeah, |
| 24 |
> they do have uses outside of desktop. |
| 25 |
|
| 26 |
Which sounds like perfect for a local setup, probably not something |
| 27 |
that should be in a generic profile. |
Archives