During a user session, gnome-settings-daemon enforces the policy for the shutdown.
There's multiple cases for "nobody is logged in". If you're running a display manager like gdm, gnome-settings-daemon is also running, which enforces the policy for shutdown. gdm runs as a special gdm user, which has its own dconf profile, so you have to configure the dconf setting for the gdm user separately at that case. If you're at a traditional console login, or at a console in general, the current session active doesn't have a registered inhibitor, so it's controlled by /etc/systemd/logind.conf. If you're curious how systemd knows when the power button is pressed, it's actually just like any other keyboard key. logind listens on every keyboard, and looks for key presses on the Power, Sleep, and Suspend keys. On Thu, Apr 10, 2014 at 9:39 AM, Charles T. Smith < [email protected]> wrote: > Charles T. Smith <cts.private.yahoo <at> gmail.com> writes: > > > > > Florian Müllner <fmuellner <at> gnome.org> writes: > > > Actually both are correct > > So, during a user session, /etc/systemd/logind.conf configures power > button > > handling, but when nobody's logged in at the user console, it's a > > Windows-Registry-like-thing, owned by a user-space app, that holds the > > configuration of how the power button is to be handled? > > > What happens when the system powers down? Is that > Windows-Registry-like-thing stored on disk in binary, a'la windows? > > _______________________________________________ > desktop-devel-list mailing list > [email protected] > https://mail.gnome.org/mailman/listinfo/desktop-devel-list > -- Jasper
_______________________________________________ desktop-devel-list mailing list [email protected] https://mail.gnome.org/mailman/listinfo/desktop-devel-list
