summaryrefslogtreecommitdiff
path: root/units/org.freedesktop.machine1.busname
diff options
context:
space:
mode:
authorDavid Herrmann <dh.herrmann@gmail.com>2014-12-16 17:30:46 +0100
committerDavid Herrmann <dh.herrmann@gmail.com>2015-03-11 12:32:48 +0100
commitb2068772f5fd05173c4a42a907e42bb69160170c (patch)
treee71199609e655d5e498f92fab760bed6f509dcc0 /units/org.freedesktop.machine1.busname
parent84c3561c58dd992b339afe5bb4c41971a2ebc486 (diff)
terminal/sysview: introduce SETTLE events
This introduces a new SYSVIEW_EVENT_SETTLE notification that is sent after initial scanning via sysview is done. This is very handy to let the application raise warnings in case requested resources are not found during startup. The SETTLE event is sent after systemd-logind and udev enumerations are done. This event does in no way guarantee that a given resource is available. All it does is notify the application that scanning is done! You must not react to SETTLE if you don't have external synchronization with the resource you're waiting for. The main use-case for SETTLE is to run applications _inside_ of logind sessions and startup sysview. You really want to make sure that the own session you're running in was found during enumeration. If not, something is seriously wrong.
Diffstat (limited to 'units/org.freedesktop.machine1.busname')
0 files changed, 0 insertions, 0 deletions