From 69b169f3532ff2502accfbcb840d56ce518f51f7 Mon Sep 17 00:00:00 2001 From: Marcel Holtmann Date: Sat, 13 Dec 2008 01:41:47 +0100 Subject: [PATCH] Add some details about the monitor-connman script --- HACKING | 24 ++++++++++++++++++++++++ 1 file changed, 24 insertions(+) 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 ==================================== -- 2.7.4