Marek Marczykowski-Górecki 643cef1e65 mgmt: send artificial 'connection-established' event just after connection ... This allows avoid race condition between registering event handlers and performing some action. The important thing is the event sent after registering event handlers in qubesd. This means state changes (like VM start/stop) after 'connection-established' event will be included in event stream. QubesOS/qubes-issues#2622		2017-05-12 14:25:28 +02:00
..
integ	Remove WrongAssignment exception	2017-04-15 23:49:39 +02:00
tools	tools: remove qvm-ls tool and related integration in qubes.property	2017-05-12 14:25:27 +02:00
vm	Fix tests broken by the new assignment api	2017-04-15 23:48:59 +02:00
__init__.py	tools: remove qvm-ls tool and related integration in qubes.property	2017-05-12 14:25:27 +02:00
app.py	qubes/events: they accept only keyword arguments	2017-02-21 14:46:42 +01:00
devices.py	Make pylint ♥	2017-04-15 23:50:11 +02:00
events.py	qubes: port core to python3	2017-01-20 16:42:51 +01:00
extra.py	qubes: port core to python3	2017-01-20 16:42:51 +01:00
firewall.py	qubes: port core to python3	2017-01-20 16:42:51 +01:00
init.py	qubes/events: they accept only keyword arguments	2017-02-21 14:46:42 +01:00
mgmt.py	mgmt: send artificial 'connection-established' event just after connection	2017-05-12 14:25:28 +02:00
run.py	qubes: port core to python3	2017-01-20 16:42:51 +01:00
storage_file.py	storage: fix handling snap_on_start=True file volumes	2017-02-14 23:59:07 +01:00
storage_lvm.py	qubes: port core to python3	2017-01-20 16:42:51 +01:00
storage.py	qubes: port core to python3	2017-01-20 16:42:51 +01:00
tarwriter.py	qubes: port core to python3	2017-01-20 16:42:51 +01:00