1 <?xml version='1.0'?> <!--*-nxml-*-->
2 <!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
3 "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
6 This file is part of systemd.
8 Copyright 2014 Zbigniew Jędrzejewski-Szmek
10 systemd is free software; you can redistribute it and/or modify it
11 under the terms of the GNU Lesser General Public License as published by
12 the Free Software Foundation; either version 2.1 of the License, or
13 (at your option) any later version.
15 systemd is distributed in the hope that it will be useful, but
16 WITHOUT ANY WARRANTY; without even the implied warranty of
17 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
18 Lesser General Public License for more details.
20 You should have received a copy of the GNU Lesser General Public License
21 along with systemd; If not, see <http://www.gnu.org/licenses/>.
25 xmlns:xi="http://www.w3.org/2001/XInclude">
29 <productname>systemd</productname>
33 <contrib>A monkey with a typewriter</contrib>
34 <firstname>Zbigniew</firstname>
35 <surname>Jędrzejewski-Szmek</surname>
36 <email>zbyszek@in.waw.pl</email>
42 <refentrytitle>busctl</refentrytitle>
43 <manvolnum>1</manvolnum>
47 <refname>busctl</refname>
48 <refpurpose>Introspect the bus</refpurpose>
53 <command>busctl</command>
54 <arg choice="opt" rep="repeat">OPTIONS</arg>
55 <arg choice="opt">COMMAND</arg>
56 <arg choice="opt" rep="repeat"><replaceable>NAME</replaceable></arg>
61 <title>Description</title>
63 <para><command>busctl</command> may be used to
64 introspect and monitor the D-Bus bus.</para>
68 <title>Options</title>
70 <para>The following options are understood:</para>
74 <term><option>--address=<replaceable>ADDRESS</replaceable></option></term>
76 <listitem><para>Connect to the bus specified by
77 <replaceable>ADDRESS</replaceable> instead of using suitable
78 defaults for either the system or user bus (see
79 <option>--system</option> and <option>--user</option>
80 options).</para></listitem>
84 <term><option>--show-machine</option></term>
86 <listitem><para>When showing the list of endpoints, show a
87 column containing the names of containers they belong to.
89 <citerefentry><refentrytitle>systemd-machined.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>.
94 <term><option>--unique</option></term>
96 <listitem><para>When showing the list of endpoints, show
97 only "unique" names (of the form
98 <literal>:<replaceable>number</replaceable>.<replaceable>number</replaceable></literal>).
103 <term><option>--acquired</option></term>
105 <listitem><para>The opposite of <option>--unique</option> —
106 only "well-known" names will be shown.</para></listitem>
110 <term><option>--activatable</option></term>
112 <listitem><para>When showing the list of endpoints, show
113 only endpoints which have actually not been activated yet,
114 but may be started automatically if accessed.</para>
119 <term><option>--match=<replaceable>MATCH</replaceable></option></term>
121 <listitem><para>When showing messages being exchanged, show only the
122 subset matching <replaceable>MATCH</replaceable>.</para></listitem>
123 <!-- TODO: link to sd_bus_add_match when it is written? -->
127 <term><option>--no-legend</option></term>
130 <para>Do not print the legend,
131 i.e. the column headers and the
137 <term><option>--size=</option></term>
140 <para>When used with the <command>capture</command> command
141 specifies the maximum bus message size to capture
142 ("snaplen"). Defaults to 4096 bytes.</para>
147 <term><option>--list</option></term>
150 <para>When used with the <command>tree</command> command shows a
151 flat list of object paths instead of a tree.</para>
156 <term><option>--quiet</option></term>
159 <para>When used with the <command>call</command> command
160 suppresses display of the response message payload. Note that even
161 if this option is specified errors returned will still be
162 printed and the tool will indicate success or failure with
163 the process exit code.</para>
168 <term><option>--verbose</option></term>
171 <para>When used with the <command>call</command> or
172 <command>get-property</command> command shows output in a
173 more verbose format.</para>
178 <term><option>--expect-reply=</option><replaceable>BOOL</replaceable></term>
181 <para>When used with the <command>call</command> command
182 specifies whether <command>busctl</command> shall wait for
183 completion of the method call, output the returned method
184 response data, and return success or failure via the process
185 exit code. If this is set to <literal>no</literal> the
186 method call will be issued but no response is expected, the
187 tool terminates immediately, and thus no response can be
188 shown, and no success or failure is returned via the exit
189 code. To only suppress output of the reply message payload
190 use <option>--quiet</option> above. Defaults to
191 <literal>yes</literal>.</para>
196 <term><option>--auto-start=</option><replaceable>BOOL</replaceable></term>
199 <para>When used with the <command>call</command> command specifies
200 whether the method call should implicitly activate the
201 called service should it not be running yet but is
202 configured to be auto-started. Defaults to
203 <literal>yes</literal>.</para>
208 <term><option>--allow-interactive-authorization=</option><replaceable>BOOL</replaceable></term>
211 <para>When used with the <command>call</command> command
212 specifies whether the services may enforce interactive
213 authorization while executing the operation, if the security
214 policy is configured for this. Defaults to
215 <literal>yes</literal>.</para>
220 <term><option>--timeout=</option><replaceable>SECS</replaceable></term>
223 <para>When used with the <command>call</command> command
224 specifies the maximum time to wait for method call
225 completion. If no time unit is specified assumes
226 seconds. The usual other units are understood, too (ms, us,
227 s, min, h, d, w, month, y). Note that this timeout does not
228 apply if <option>--expect-reply=no</option> is used as the
229 tool does not wait for any reply message then. When not
230 specified or when set to 0 the default of
231 <literal>25s</literal> is assumed.</para>
235 <xi:include href="user-system-options.xml" xpointer="user" />
236 <xi:include href="user-system-options.xml" xpointer="system" />
237 <xi:include href="user-system-options.xml" xpointer="host" />
238 <xi:include href="user-system-options.xml" xpointer="machine" />
240 <xi:include href="standard-options.xml" xpointer="help" />
241 <xi:include href="standard-options.xml" xpointer="version" />
242 <xi:include href="standard-options.xml" xpointer="no-pager" />
247 <title>Commands</title>
249 <para>The following commands are understood:</para>
253 <term><command>list</command></term>
255 <listitem><para>Show service names on the bus. This is the
256 default if no command is specified.</para></listitem>
260 <term><command>status</command> <arg choice="plain"><replaceable>SERVICE</replaceable></arg></term>
262 <listitem><para>Show process information and credentials of a
263 bus service.</para></listitem>
267 <term><command>monitor</command> <arg choice="opt" rep="repeat"><replaceable>SERVICE</replaceable></arg></term>
269 <listitem><para>Dump messages being exchanged. If
270 <replaceable>SERVICE</replaceable> is specified, show messages
271 to or from this endpoint. Otherwise, show all messages on the
272 bus. Use Ctrl-C to terminate dump.</para></listitem>
276 <term><command>capture</command> <arg choice="opt" rep="repeat"><replaceable>SERVICE</replaceable></arg></term>
278 <listitem><para>Similar to <command>monitor</command> but
279 writes the output in pcap format (for details see the <ulink
280 url="http://wiki.wireshark.org/Development/LibpcapFileFormat">Libpcap
281 File Format</ulink> description. Make sure to redirect the
282 output to STDOUT to a file. Tools like
283 <citerefentry><refentrytitle>wireshark</refentrytitle><manvolnum>1</manvolnum></citerefentry>
284 may be used to dissect and view the generated
285 files.</para></listitem>
289 <term><command>tree</command> <arg choice="opt" rep="repeat"><replaceable>SERVICE</replaceable></arg></term>
291 <listitem><para>Shows an object tree of one or more
292 services. If <replaceable>SERVICE</replaceable> is specified,
293 show object tree of the specified services only. Otherwise,
294 show all object trees of all services on the bus that acquired
295 at least one well-known name.</para></listitem>
299 <term><command>introspect</command> <arg choice="plain"><replaceable>SERVICE</replaceable></arg> <arg choice="plain"><replaceable>OBJECT</replaceable></arg></term>
301 <listitem><para>Show interfaces, methods, properties and
302 signals of the specified object (identified by its path) on
303 the specified service.</para></listitem>
307 <term><command>call</command> <arg choice="plain"><replaceable>SERVICE</replaceable></arg> <arg choice="plain"><replaceable>OBJECT</replaceable></arg> <arg choice="plain"><replaceable>INTERFACE</replaceable></arg> <arg choice="plain"><replaceable>METHOD</replaceable></arg> <arg choice="opt"><replaceable>SIGNATURE</replaceable> <arg choice="opt" rep="repeat"><replaceable>ARGUMENT</replaceable></arg></arg></term>
309 <listitem><para>Invoke a method and show the response. Takes a
310 service name, object path, interface name and method name. If
311 parameters shall be passed to the method call a signature
312 string is required, followed by the arguments, individually
313 formatted as strings. For details on the formatting used, see
314 below. To suppress output of the returned data use the
315 <option>--quiet</option> option.</para></listitem>
319 <term><command>get-property</command> <arg choice="plain"><replaceable>SERVICE</replaceable></arg> <arg choice="plain"><replaceable>OBJECT</replaceable></arg> <arg choice="plain"><replaceable>INTERFACE</replaceable></arg> <arg choice="plain" rep="repeat"><replaceable>PROPERTY</replaceable></arg></term>
321 <listitem><para>Retrieve the current value of one or more
322 object properties. Takes a service name, object path,
323 interface name and property name. Multiple properties may be
324 specified at once in which case their values will be shown one
325 after the other, separated by newlines. The output is by
326 default in terse format. Use <option>--verbose</option> for a
327 more elaborate output format.</para></listitem>
331 <term><command>set-property</command> <arg choice="plain"><replaceable>SERVICE</replaceable></arg> <arg choice="plain"><replaceable>OBJECT</replaceable></arg> <arg choice="plain"><replaceable>INTERFACE</replaceable></arg> <arg choice="plain"><replaceable>PROPERTY</replaceable></arg> <arg choice="plain"><replaceable>SIGNATURE</replaceable></arg> <arg choice="plain" rep="repeat"><replaceable>ARGUMENT</replaceable></arg></term>
333 <listitem><para>Set the current value an object
334 property. Takes a service name, object path, interface name,
335 property name, property signature, followed by a list of
336 parameters formatted as strings.</para></listitem>
340 <term><command>help</command></term>
342 <listitem><para>Show command syntax help.</para></listitem>
348 <title>Parameter Formatting</title>
350 <para>The <command>call</command> and
351 <command>set-property</command> commands take a signature
352 string followed by a list of parameters formatted as string
353 (for details on D-Bus signature strings see the <ulink
354 url="http://dbus.freedesktop.org/doc/dbus-specification.html#type-system">Type
355 system chapter of the D-Bus specification</ulink>). For
356 simple types each parameter following the signature should
357 simply be the parameter's value formatted as
358 string. Positive boolean values may be formatted as
359 <literal>true</literal>, <literal>yes</literal>,
360 <literal>on</literal>, <literal>1</literal>; negative
361 boolean values may be specified as <literal>false</literal>,
362 <literal>no</literal>, <literal>off</literal>,
363 <literal>0</literal>. For arrays, a numeric argument for the
364 number of entries followed by the entries shall be
365 specified. For variants the signature of the contents shall
366 be specified, followed by the contents. For dictionaries and
367 structs the contents of them shall be directly
371 <programlisting>s jawoll</programlisting> is the formatting
372 of a single string <literal>jawoll</literal>.</para>
375 <programlisting>as 3 hello world foobar</programlisting>
376 is the formatting of a string array with three entries,
377 <literal>hello</literal>, <literal>world</literal> and
378 <literal>foobar</literal>.</para>
381 <programlisting>a{sv} 3 One s Eins Two u 2 Yes b true</programlisting>
382 is the formatting of a dictionary
383 array that maps strings to variants, consisting of three
384 entries. The string <literal>One</literal> is assigned the
385 string <literal>Eins</literal>. The string
386 <literal>Two</literal> is assigned the 32bit unsigned
387 integer 2. The string <literal>Yes</literal> is assigned a
388 positive boolean.</para>
390 <para>Note that the <command>call</command>,
391 <command>get-property</command>,
392 <command>introspect</command> commands will also generate
393 output in this format for the returned data. Since this
394 format is sometimes too terse to be easily understood, the
395 <command>call</command> and <command>get-property</command>
396 commands may generate a more verbose, multi-line output when
397 passed the <option>--verbose</option> option.</para>
401 <title>Examples</title>
404 <title>Write and Read a Property</title>
406 <para>The following two commands first write a
407 property and then read it back. The property is
409 <literal>/org/freedesktop/systemd1</literal> object
410 of the <literal>org.freedesktop.systemd1</literal>
411 service. The name of the property is
412 <literal>LogLevel</literal> on the
413 <literal>org.freedesktop.systemd1.Manager</literal>
414 interface. The property contains a single
417 <programlisting># busctl set-property org.freedesktop.systemd1 /org/freedesktop/systemd1 org.freedesktop.systemd1.Manager LogLevel s debug
418 # busctl get-property org.freedesktop.systemd1 /org/freedesktop/systemd1 org.freedesktop.systemd1.Manager LogLevel
419 s "debug"</programlisting>
424 <title>Terse and Verbose Output</title>
426 <para>The following two commands read a property that
427 contains an array of strings, and first show it in
428 terse format, followed by verbose format:</para>
430 <programlisting>$ busctl get-property org.freedesktop.systemd1 /org/freedesktop/systemd1 org.freedesktop.systemd1.Manager Environment
431 as 2 "LANG=en_US.UTF-8" "PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin"
432 $ busctl get-property --verbose org.freedesktop.systemd1 /org/freedesktop/systemd1 org.freedesktop.systemd1.Manager Environment
434 STRING "LANG=en_US.UTF-8";
435 STRING "PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin";
440 <title>Invoking a Method</title>
442 <para>The following command invokes a the
443 <literal>StartUnit</literal> method on the
444 <literal>org.freedesktop.systemd1.Manager</literal>
446 <literal>/org/freedesktop/systemd1</literal> object
447 of the <literal>org.freedesktop.systemd1</literal>
448 service, and passes it two strings
449 <literal>cups.service</literal> and
450 <literal>replace</literal>. As result of the method
451 call a single object path parameter is received and
454 <programlisting># busctl call org.freedesktop.systemd1 /org/freedesktop/systemd1 org.freedesktop.systemd1.Manager StartUnit ss "cups.service" "replace"
455 o "/org/freedesktop/systemd1/job/42684"</programlisting>
460 <title>See Also</title>
463 <citerefentry><refentrytitle>dbus-daemon</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
464 <ulink url="http://freedesktop.org/wiki/Software/dbus">D-Bus</ulink>,
465 <ulink url="https://code.google.com/p/d-bus/">kdbus</ulink>,
466 <citerefentry><refentrytitle>sd-bus</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
467 <citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
468 <citerefentry><refentrytitle>systemd-bus-proxyd</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
469 <citerefentry><refentrytitle>machinectl</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
470 <citerefentry><refentrytitle>wireshark</refentrytitle><manvolnum>1</manvolnum></citerefentry>