summaryrefslogtreecommitdiff
path: root/HACKING
diff options
context:
space:
mode:
authorMarcel Holtmann <marcel@holtmann.org>2008-12-13 00:41:47 (GMT)
committerMarcel Holtmann <marcel@holtmann.org>2008-12-13 00:41:47 (GMT)
commit69b169f3532ff2502accfbcb840d56ce518f51f7 (patch)
tree12823de9b54d1d49b63375a6d5da3bbd31d6f2c4 /HACKING
parentd6253a89c45aee2e7d6928d3f1ab6ea5d96e6774 (diff)
downloadconnman-69b169f3532ff2502accfbcb840d56ce518f51f7.zip
connman-69b169f3532ff2502accfbcb840d56ce518f51f7.tar.gz
connman-69b169f3532ff2502accfbcb840d56ce518f51f7.tar.bz2
Add some details about the monitor-connman script
Diffstat (limited to 'HACKING')
-rw-r--r--HACKING24
1 files changed, 24 insertions, 0 deletions
diff --git a/HACKING b/HACKING
index 221bfed..baf7ccd 100644
--- a/HACKING
+++ b/HACKING
@@ -90,6 +90,30 @@ line switch allows to specify a glob pattern for the interface names.
# sudo ./src/connmand -n -i wlan*
+Debugging the D-Bus interface during runtime
+============================================
+
+Running the daemon with debugging information in the foreground is quite
+verbose and sometimes not really helpful. The "monitor-connman" script
+allows to monitor "PropertyChanged" D-Bus signals from various interfaces.
+
+ During start of daemon
+ {Manager} [/] Devices = dbus.Array([dbus.ObjectPath('/dev_00_90_CC ...
+ {Device} [/dev_00_90_CC_xx_xx_xx] Powered = 1
+ {Device} [/dev_00_90_CC_xx_xx_xx] Networks = dbus.Array( ...
+
+ During shutdown of daemon
+ {Device} [/dev_00_90_CC_xx_xx_xx] Networks = dbus.Array( ...
+ {Device} [/dev_00_90_CC_xx_xx_xx] Powered = 0
+ {Manager} [/] Devices = dbus.Array([], ...
+
+Every "PropertyChanged" signal will generate a line of output. Some of them
+can get very complex. The first detail inside "{ ... }" is the interface
+name (without its service name prefix). The second detail inside "[ ... ]"
+is the object path. And after that it is followed by a key and value of
+the property that changed.
+
+
Generating source code documentation
====================================