summaryrefslogtreecommitdiff
path: root/introspection
diff options
context:
space:
mode:
authorDan Winship <danw@gnome.org>2013-08-13 17:45:34 -0400
committerDan Winship <danw@gnome.org>2013-08-16 17:27:34 -0400
commitbc091f2f3ea2ee27d012f2332c514516fd61441b (patch)
tree8fb8b00a6b51203564185ae674518cea99887f5b /introspection
parentcee676e7048313af32a31b18846f522fff3ec5d5 (diff)
downloadNetworkManager-bc091f2f3ea2ee27d012f2332c514516fd61441b.tar.gz
core: add NMManager:startup property
Add a property on NMManager indicating that it is currently starting up and activating startup-time/boot-time network connections. "startup" is initially TRUE, and becomes FALSE once all NMDevices report that they have no pending activity (eg, trying to activate, waiting for a wifi scan to complete, etc). This is tracked via a new NMDevice:has-pending-activity property, which is maintained partially by the device itself, and partially by other parts of the code.
Diffstat (limited to 'introspection')
-rw-r--r--introspection/nm-manager.xml8
1 files changed, 8 insertions, 0 deletions
diff --git a/introspection/nm-manager.xml b/introspection/nm-manager.xml
index 6f3c8cac6a..d9f6a7c3d2 100644
--- a/introspection/nm-manager.xml
+++ b/introspection/nm-manager.xml
@@ -302,6 +302,14 @@
</tp:docstring>
</property>
+ <property name="Startup" type="b" access="read">
+ <tp:docstring>
+ Indicates whether NM is still starting up; this becomes FALSE
+ when NM has finished attempting to activate every connection
+ that it might be able to activate at startup.
+ </tp:docstring>
+ </property>
+
<property name="Version" type="s" access="read">
<tp:docstring>
NetworkManager version.