On Mon, Jan 06, 2020 at 09:10:44AM -0500, Hendrik Boom wrote: > On Mon, Jan 06, 2020 at 01:53:09PM +0000, Mark Hindley wrote: > > On Mon, Jan 06, 2020 at 08:39:45AM -0500, Hendrik Boom wrote: > > > Just wondering -- did it refuse to boot or be otherwise seriously > > > unusable until you had installed elogind and libelogind0? Were your > > > text-only consoles affected? Or did it just interfere with desktops? > > > > > > And just curious -- never heard of these before systemd. What do they > > > do? > > > > >From https://github.com/elogind/elogind/: > > > > 'The systemd project's "logind", extracted to a standalone package' > > > > It keeps a record of logins, seats and sessions and maps pids to those so > > that > > desktoppy things like being able to reboot from the desktop work without > > having > > to become root. > > I see. So in effect it provides a privilege check on rebooting.
Indirectly. policykit-1 does the checking, but asks elogind or consolekit if the requesting pid is part of the session that it claims. Mark _______________________________________________ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
