From: Andrew Zaborowski <andrew.zaborowski@intel.com>
To: iwd@lists.01.org
Subject: [PATCH 2/2] doc: Daemon DBus interface documentation
Date: Thu, 06 May 2021 23:28:28 +0200 [thread overview]
Message-ID: <20210506212828.79315-2-andrew.zaborowski@intel.com> (raw)
In-Reply-To: <20210506212828.79315-1-andrew.zaborowski@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1122 bytes --]
---
doc/daemon-api.txt | 24 ++++++++++++++++++++++++
1 file changed, 24 insertions(+)
create mode 100644 doc/daemon-api.txt
diff --git a/doc/daemon-api.txt b/doc/daemon-api.txt
new file mode 100644
index 00000000..8256bb10
--- /dev/null
+++ b/doc/daemon-api.txt
@@ -0,0 +1,24 @@
+Daemon hierarchy
+================
+
+Service net.connman.iwd
+Interface net.connman.iwd.Daemon [Experimental]
+Object path /net/connman/iwd
+
+Methods dict GetInfo()
+
+ Returns basic IWD daemon's status and configuration
+ properties. Their values are global and may be useful
+ for D-Bus clients interacting with IWD, not so much
+ for the user. The returned dictionary (a{sv}) maps
+ string keys to values of types defined per key.
+ Clients should ignore unknown keys.
+
+ The following key/value pairs are defined currently:
+
+ string Version - IWD release version,
+
+ string StateDirectory - Absolute path to the IWD
+ state directory where network configuration and
+ runtime state files are kept (see $STATE_DIRECTORY in
+ iwd(8) and iwd.network(5)).
--
2.27.0
next prev parent reply other threads:[~2021-05-06 21:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-06 21:28 [PATCH 1/2] main: Add D-Bus Daemon.GetInfo method Andrew Zaborowski
2021-05-06 21:28 ` Andrew Zaborowski [this message]
2021-05-07 13:44 ` Denis Kenzior
-- strict thread matches above, loose matches on Subject: below --
2021-05-05 22:29 Andrew Zaborowski
2021-05-05 22:29 ` [PATCH 2/2] doc: Daemon DBus interface documentation Andrew Zaborowski
2021-05-06 16:20 ` Ryan Smith
2021-05-06 20:52 ` Andrew Zaborowski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210506212828.79315-2-andrew.zaborowski@intel.com \
--to=andrew.zaborowski@intel.com \
--cc=iwd@lists.01.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.