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