like this:
Checkout repository
- # git-clone git://git.moblin.org/projects/connman.git
+ # git clone git://git.kernel.org/pub/scm/network/connman/connman.git
# cd connman
Configure and build
automatically includes this option.
Run daemon in foreground with debugging
- # sudo ./src/connmand -n -d
+ # sudo ./src/connmand -n -d 'plugins/*'
+
+The debugging option -d takes an argument. This argument can be a comma
+separated list of file names like 'plugins/wifi.c,plugins/ethernet.c' to
+enable debugs in these files. Simple glob style pattern matching is
+supported in this list.
For production installations or distribution packaging it is important that
the "--enable-maintainer-mode" option is NOT used.
# sudo ./src/connmand -n -i wlan*
-Generating source code documentation
-====================================
-
-The source code is annotated using the gtk-doc style documentation. This
-allows an easy way of generating API documentation. The "bootstrap-configure"
-script will use the "--enable-gtk-doc" configure to enable the generation of
-the documentation.
-
-To make the gtk-doc process work, the gtk-doc tools need to be installed.
-Every distribution should provide a package for this, but the naming of the
-package might be different:
-
- Ubuntu/Debian
- # apt-get install gtk-doc-utils
-
- Fedora
- # yum install gtk-doc
-
-In case "bootstrap-configure" is not used, the manual steps for generating
-the documentation files are like this:
-
- Configuring the repository
- # ./configure --enable-gtk-doc
-
- Generate the documentation
- # cd doc && make
+Debugging the D-Bus interface during runtime
+============================================
- View documentation
- # firefox doc/html/index.html
+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.
+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.