source: general/sysutils/dbus.xml@ f29eb8a

10.0 10.1 11.0 8.1 8.2 8.3 8.4 9.0 9.1 basic bdubbs/svn elogind ken/refactor-virt lazarus perl-modules qt5new trunk upgradedb xry111/git-date xry111/git-date-for-trunk xry111/git-date-test
Last change on this file since f29eb8a was f29eb8a, checked in by DJ Lucas <dj@…>, 5 years ago

Enabled user session support in DBus (systemd only) and use real path for PID file and system socket, Added sed command to differentiate between Plasma sessions on Xorg and Wayland in display managers.

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@18533 af4574ff-66df-0310-9fd7-8a98e5e911e0

  • Property mode set to 100644
File size: 25.4 KB
Line 
1<?xml version="1.0" encoding="ISO-8859-1"?>
2<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
3 "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
4 <!ENTITY % general-entities SYSTEM "../../general.ent">
5 %general-entities;
6
7 <!ENTITY dbus-download-http "http://dbus.freedesktop.org/releases/dbus/dbus-&dbus-version;.tar.gz">
8 <!ENTITY dbus-download-ftp " ">
9 <!ENTITY dbus-md5sum "7f06c43736874c1ff50ae20392955511">
10 <!ENTITY dbus-size "1.9 MB">
11 <!ENTITY dbus-buildsize "27 MB (add 23 MB for the tests)">
12 <!ENTITY dbus-time "0.3 SBU (add 2 SBU for the tests)">
13]>
14
15<sect1 id="dbus" xreflabel="dbus-&dbus-version;">
16 <?dbhtml filename="dbus.html"?>
17
18 <sect1info>
19 <othername>$LastChangedBy$</othername>
20 <date>$Date$</date>
21 </sect1info>
22
23 <title>dbus-&dbus-version;</title>
24
25 <indexterm zone="dbus">
26 <primary sortas="a-D-Bus">D-Bus</primary>
27 </indexterm>
28
29 <sect2 role="package">
30 <title>Introduction to D-Bus</title>
31
32 <para revision="sysv">
33 <application>D-Bus</application> is a message bus system, a simple way
34 for applications to talk to one another.
35 <application>D-Bus</application> supplies both a system daemon (for
36 events such as <quote>new hardware device added</quote> or <quote>printer
37 queue changed</quote>) and a per-user-login-session daemon (for general
38 IPC needs among user applications). Also, the message bus is built on top
39 of a general one-to-one message passing framework, which can be used by
40 any two applications to communicate directly (without going through the
41 message bus daemon).
42 </para>
43
44 <para revision="systemd">
45 Even though <application>D-Bus</application> was built in LFS, there are
46 some features provided by the package that other BLFS packages need, but
47 their dependencies didn't fit into LFS.
48 </para>
49
50 &lfs80_checked;
51
52 <bridgehead renderas="sect3">Package Information</bridgehead>
53 <itemizedlist spacing="compact">
54 <listitem>
55 <para>
56 Download (HTTP): <ulink url="&dbus-download-http;"/>
57 </para>
58 </listitem>
59 <listitem>
60 <para>
61 Download (FTP): <ulink url="&dbus-download-ftp;"/>
62 </para>
63 </listitem>
64 <listitem>
65 <para>
66 Download MD5 sum: &dbus-md5sum;
67 </para>
68 </listitem>
69 <listitem>
70 <para>
71 Download size: &dbus-size;
72 </para>
73 </listitem>
74 <listitem>
75 <para>
76 Estimated disk space required: &dbus-buildsize;
77 </para>
78 </listitem>
79 <listitem>
80 <para>
81 Estimated build time: &dbus-time;
82 </para>
83 </listitem>
84 </itemizedlist>
85
86 <bridgehead renderas="sect3">D-Bus Dependencies</bridgehead>
87
88<!--
89 <bridgehead renderas="sect4">Required</bridgehead>
90 <para role="required">
91 <xref linkend="expat"/>
92 </para>
93-->
94 <bridgehead renderas="sect4" revision="systemd">Required</bridgehead>
95 <para role="required" revision="systemd">
96 <xref linkend="systemd"/>
97 </para>
98
99 <bridgehead renderas="sect4">Recommended</bridgehead>
100 <para role="recommended">
101 <xref linkend="xorg7-lib"/> (for <command>dbus-launch</command> program)
102 </para>
103
104 <bridgehead renderas="sect4">Optional</bridgehead>
105 <para role="optional">
106 For the tests:
107 <xref linkend="dbus-glib"/>,
108 <xref linkend="dbus-python"/>,
109 <xref linkend="pygobject2"/> (built with gobject-introspection support),
110 and <xref linkend="valgrind"/>;
111
112 for documentation:
113 <xref linkend="doxygen"/>,
114 <xref linkend="xmlto"/>,
115 <ulink url="https://pypi.python.org/pypi/mallard-ducktype">Ducktype</ulink>,
116 and
117 <ulink url="http://ftp.gnome.org/pub/gnome/sources/yelp-tools/">Yelp Tools</ulink>
118 </para>
119
120 <para condition="html" role="usernotes">User Notes:
121 <ulink url="&blfs-wiki;/dbus"/>
122 </para>
123 </sect2>
124
125 <sect2 role="installation">
126 <title>Installation of D-Bus</title>
127
128 <para revision="sysv">
129 If they do not already exist,
130 as the <systemitem class="username">root</systemitem> user, create a
131 system user and group to handle the system message bus activity:
132 </para>
133
134<screen role="root" revision="sysv"><userinput>groupadd -g 18 messagebus &amp;&amp;
135useradd -c "D-Bus Message Daemon User" -d /var/run/dbus \
136 -u 18 -g messagebus -s /bin/false messagebus</userinput></screen>
137
138 <para>
139 Install <application>D-Bus</application> by running the following
140 commands (you may wish to review the output from <command>./configure
141 --help</command> first and add any desired parameters to the
142 <command>configure</command> command shown below):
143 </para>
144
145<screen revision="sysv"><userinput>./configure --prefix=/usr \
146 --sysconfdir=/etc \
147 --localstatedir=/var \
148 --disable-doxygen-docs \
149 --disable-xml-docs \
150 --disable-static \
151 --docdir=/usr/share/doc/dbus-&dbus-version; \
152 --with-console-auth-dir=/run/console \
153 --with-system-pid-file=/run/dbus/pid \
154 --with-system-socket=/run/dbus/system_bus_socket &amp;&amp;
155make</userinput></screen>
156
157<screen revision="systemd"><userinput>./configure --prefix=/usr \
158 --sysconfdir=/etc \
159 --localstatedir=/var \
160 --enable-user-session \
161 --disable-doxygen-docs \
162 --disable-xml-docs \
163 --disable-static \
164 --docdir=/usr/share/doc/dbus-&dbus-version; \
165 --with-console-auth-dir=/run/console \
166 --with-system-pid-file=/run/dbus/pid \
167 --with-system-socket=/run/dbus/system_bus_socket &amp;&amp;
168make</userinput></screen>
169
170 <para>
171 See below for test instructions.
172 </para>
173
174 <warning revision="systemd">
175 <para>
176 Installing the package will override all files installed by
177 <application>D-Bus</application> in LFS. It is critical that
178 nothing uses <application>D-Bus</application> libraries or
179 programs during the installation. The best way to ensure that these
180 libraries are not being used is to run the installation in rescue mode.
181 To switch to rescue mode, run the following command as the
182 <systemitem class="username">root</systemitem> user (from a TTY):
183 </para>
184
185<screen role="root"><userinput>systemctl start rescue.target</userinput></screen>
186
187 </warning>
188
189 <para>
190 Now, as the <systemitem class="username">root</systemitem> user:
191 </para>
192
193<screen role="root"><userinput>make install</userinput></screen>
194
195 <para revision="systemd">
196 The shared library needs to be moved to
197 <filename class="directory">/lib</filename>, and as a result the
198 <filename class="extension">.so</filename> file in
199 <filename class="directory">/usr/lib</filename> will need to be
200 recreated. Run the following command as the
201 <systemitem class="username">root</systemitem> user:
202 </para>
203
204<screen revision="systemd" role="root"><userinput>mv -v /usr/lib/libdbus-1.so.* /lib
205ln -sfv ../../lib/$(readlink /usr/lib/libdbus-1.so) /usr/lib/libdbus-1.so</userinput></screen>
206
207 <para>
208 If you are using a DESTDIR install,
209 <command>dbus-daemon-launch-helper</command> needs to be fixed
210 afterwards. Issue, as <systemitem class="username">root</systemitem>
211 user:
212 </para>
213
214<screen role="root"><userinput>chown -v root:messagebus /usr/libexec/dbus-daemon-launch-helper &amp;&amp;
215chmod -v 4750 /usr/libexec/dbus-daemon-launch-helper</userinput></screen>
216
217 <para revision="sysv">
218 If you are still building your system in chroot or you did not start the
219 daemon yet, but you want to compile some packages that require
220 <application>D-Bus</application>, generate
221 <application>D-Bus</application> UUID to avoid warnings when compiling
222 some packages with the following command as the
223 <systemitem class="username">root</systemitem> user:
224 </para>
225
226<screen role="root" revision="sysv"><userinput>dbus-uuidgen --ensure</userinput></screen>
227
228 <para revision="systemd">
229 If not in chroot, at this point, you should reload the systemd daemon,
230 and reenter multi-user mode with the following commands (as the
231 <systemitem class="username">root</systemitem> user):
232 </para>
233
234<screen role="root" revision="systemd"><userinput>systemctl daemon-reload
235systemctl start multi-user.target</userinput></screen>
236
237 <para>
238 The dbus tests cannot be run until after <xref linkend="dbus-glib"/> has
239 been installed. They must be run as an unprivileged user from a local
240 session with bus address. Tests fail through ssh. If you want to run only
241 the unit tests, replace, below, <parameter>--enable-tests</parameter> by
242 <parameter>--enable-embedded-tests</parameter>, otherwise, <xref
243 linkend="dbus-python"/> has to be installed, before. The tests require
244 passing additional parameters to <command>configure</command> and
245 exposing additional functionality in the binaries. These interfaces are
246 not intended to be used in a production build of
247 <application>D-Bus</application>. If you would like to run the tests,
248 issue the following commands (for the tests, you don't need to build the
249 docs):
250 </para>
251
252<screen><userinput>make distclean &amp;&amp;
253./configure --enable-tests \
254 --enable-asserts \
255 --disable-doxygen-docs \
256 --disable-xml-docs &amp;&amp;
257make &amp;&amp;
258make check</userinput></screen>
259
260 <para>
261 The <quote>estimated disk space required</quote> reported above is
262 obtained in a build using the switches disabling documents generation.
263 This and the use of the <command>make distclean</command> command implies
264 that the build directory size is smaller than the one for a full build
265 with documents generated. There is one error, test-bus.sh, for unknown
266 reasons.
267 </para>
268<!--
269 <para>
270 If <command>run-test.sh</command> fails, it can be disabled with the
271 following sed, before running the commands for the tests:
272 </para>
273
274<screen><userinput>sed -i -e 's:run-test.sh:$(NULL):g' test/name-test/Makefile.in</userinput></screen>-->
275
276 <para>
277 There has been a report that the tests may fail if running inside a
278 Midnight Commander shell. You may get out-of-memory error messages when
279 running the tests. These are normal and can be safely ignored.
280 </para>
281
282 </sect2>
283
284 <sect2 role="commands">
285 <title>Command Explanations</title>
286
287 <para>
288 <parameter>--disable-doxygen-docs</parameter>: This switch disables
289 doxygen documentation build and install, if you have
290 <application>doxygen</application> installed. If
291 <application>doxygen</application> is installed, and you wish to build
292 them, remove this parameter.
293 </para>
294
295 <para>
296 <parameter>--disable-xml-docs</parameter>: This switch disables html
297 documentation build and install, if you have
298 <application>xmlto</application> installed. If
299 <application>xmlto</application> is installed, and you wish to build
300 them, remove this parameter.
301 </para>
302
303 <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
304 href="../../xincludes/static-libraries.xml"/>
305
306 <para revision="sysv">
307 <parameter>--disable-systemd</parameter>: This switch disables systemd
308 support in <application>D-Bus</application>.
309 </para>
310
311 <para revision="sysv">
312 <parameter>--without-systemdsystemunitdir</parameter>: This switch
313 prevents installation of systemd unit files.
314 </para>
315
316 <para revision="systemd">
317 <parameter>--enable-user-session</parameter>: This parameter enables
318 per-user DBus sessions with <application>systemd</application>.
319 </para>
320
321 <para>
322 <parameter>--with-console-auth-dir=/run/console/</parameter>: This
323 parameter specifies location of the
324 <application>ConsoleKit</application> auth dir.
325 </para>
326
327 <para>
328 <parameter>--with-system-pid-file=/run/dbus/pid</parameter>: This
329 parameter specifies the location of the PID file.
330 </para>
331
332 <para>
333 <parameter>--with-system-socket=/run/dbus/system_bus_socket</parameter>:
334 This parameter specifies the location of the system bus socket.
335 </para>
336
337 <para>
338 <parameter>--enable-tests</parameter>: Build extra parts of the code to
339 support all tests. Configure will end with a NOTE warning about increased
340 size of libraries and decreased security.
341 </para>
342
343 <para>
344 <option>--enable-embedded-tests</option>: Build extra parts of the
345 code to support only unit tests. Configure will end with a NOTE warning
346 about increased size of libraries and decreased security.
347 </para>
348
349 <para>
350 <parameter>--enable-asserts</parameter>: Enable debugging code to run
351 assertions for statements normally assumed to be true. This prevents a
352 warning that '<parameter>--enable-tests</parameter>' on its own is only
353 useful for profiling and might not give true results for all tests, but
354 adds its own NOTE that this should not be used in a production build.
355 </para>
356
357 </sect2>
358
359 <sect2 role="configuration">
360 <title>Configuring D-Bus</title>
361
362 <sect3 id="dbus-config">
363 <title>Config Files</title>
364
365 <para>
366 <filename>/etc/dbus-1/session.conf</filename>,
367 <filename>/etc/dbus-1/system.conf</filename> and
368 <filename>/etc/dbus-1/system.d/*</filename>
369 </para>
370
371 <indexterm zone="dbus dbus-config">
372 <primary sortas="e-etc-dbus-1-session.conf">/etc/dbus-1/session.conf</primary>
373 </indexterm>
374
375 <indexterm zone="dbus dbus-config">
376 <primary sortas="e-etc-dbus-1/system.conf">/etc/dbus-1/system.conf</primary>
377 </indexterm>
378
379 <indexterm zone="dbus dbus-config">
380 <primary sortas="e-etc-dbus-1-system.d-star">/etc/dbus-1/system.d/*</primary>
381 </indexterm>
382
383 </sect3>
384
385 <sect3 id="dbus-session-config" xreflabel="D-Bus custom services directory">
386 <title>Configuration Information</title>
387
388 <para>
389 The configuration files listed above should probably not be
390 modified. If changes are required, you should create
391 <filename>/etc/dbus-1/session-local.conf</filename> and/or
392 <filename>/etc/dbus-1/system-local.conf</filename> and make any
393 desired changes to these files.
394 </para>
395
396 <para>
397 If any packages install a
398 <application>D-Bus</application> <filename>.service</filename>
399 file outside of the standard <filename
400 class="directory">/usr/share/dbus-1/services</filename> directory,
401 that directory should be added to the local session configuration.
402 For instance, <filename
403 class="directory">/usr/local/share/dbus-1/services</filename> can
404 be added by performing the following commands as the
405 <systemitem class="username">root</systemitem> user:
406 </para>
407
408<screen role="root"><userinput>cat &gt; /etc/dbus-1/session-local.conf &lt;&lt; "EOF"
409<literal>&lt;!DOCTYPE busconfig PUBLIC
410 "-//freedesktop//DTD D-BUS Bus Configuration 1.0//EN"
411 "http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd"&gt;
412&lt;busconfig&gt;
413
414 &lt;!-- Search for .service files in /usr/local --&gt;
415 &lt;servicedir&gt;/usr/local/share/dbus-1/services&lt;/servicedir&gt;
416
417&lt;/busconfig&gt;</literal>
418EOF</userinput></screen>
419
420 </sect3>
421
422 <sect3 id="dbus-session">
423 <title>D-Bus Session Daemon</title>
424
425 <para revision="sysv">
426 To automatically start <command>dbus-daemon</command> when the
427 system is rebooted, install the
428 <filename>/etc/rc.d/init.d/dbus</filename> bootscript from the
429 <xref linkend="bootscripts"/> package.
430 </para>
431
432 <indexterm zone="dbus dbus-session" revision="sysv">
433 <primary sortas="f-dbus">dbus</primary>
434 </indexterm>
435
436<screen role="root" revision="sysv"><userinput>make install-dbus</userinput></screen>
437
438 <para revision="sysv">
439 Note that this boot script only starts the system-wide
440 <application>D-Bus</application> daemon. Each user requiring access to
441 <application>D-Bus</application> services will also need to run a
442 session daemon as well. There are many methods you can use to start a
443 session daemon using the <command>dbus-launch</command> command. Review
444 the <command>dbus-launch</command> man page for details about the
445 available parameters and options. Here are some suggestions and
446 examples:
447 </para>
448
449 <para revision="systemd">
450 There are many methods you can use to start a session daemon
451 using the <command>dbus-launch</command> command. Review the
452 <command>dbus-launch</command> man page for details about the
453 available parameters and options. Here are some suggestions and
454 examples:
455 </para>
456
457
458 <itemizedlist spacing="compact">
459 <listitem>
460 <para>
461 Add <command>dbus-launch</command> to the line in the
462 <filename>~/.xinitrc</filename> file that starts your graphical
463 desktop environment.
464 </para>
465 </listitem>
466 <listitem>
467 <para>
468 If you use <command>xdm</command> or some other display manager
469 that calls the <filename>~/.xsession</filename> file, you can add
470 <command>dbus-launch</command> to the line in your
471 <filename>~/.xsession</filename> file that starts your graphical
472 desktop environment. The syntax would be similar to the example in
473 the <filename>~/.xinitrc</filename> file.
474 </para>
475 </listitem>
476 <listitem>
477 <para>
478 The examples shown previously use
479 <command>dbus-launch</command> to specify a program to be run. This
480 has the benefit (when also using the
481 <parameter>--exit-with-session</parameter> parameter) of stopping the
482 session daemon when the specified program is stopped. You can also
483 start the session daemon in your system or personal startup scripts
484 by adding the following lines:
485 </para>
486
487<screen role="nodump"><userinput><literal># Start the D-Bus session daemon
488eval `dbus-launch`
489export DBUS_SESSION_BUS_ADDRESS</literal></userinput></screen>
490
491 <para>
492 This method will not stop the session daemon when you exit
493 your shell, therefore you should add the following line to your
494 <filename>~/.bash_logout</filename> file:
495 </para>
496
497<screen role="nodump"><userinput><literal># Kill the D-Bus session daemon
498kill $DBUS_SESSION_BUS_PID</literal></userinput></screen>
499 </listitem>
500
501 <listitem>
502 <para>
503 A hint has been written that provides ways to start scripts
504 using the KDM session manager of KDE. The concepts in this hint could
505 possibly be used with other session managers as well. The hint is
506 located at <ulink
507 url="&hints-root;/downloads/files/execute-session-scripts-using-kdm.txt"/>.
508 </para>
509 </listitem>
510
511 </itemizedlist>
512
513 </sect3>
514
515 </sect2>
516
517 <sect2 role="content" revision="sysv">
518 <title>Contents</title>
519
520 <segmentedlist>
521 <segtitle>Installed Programs</segtitle>
522 <segtitle>Installed Library</segtitle>
523 <segtitle>Installed Directories</segtitle>
524
525 <seglistitem>
526 <seg>
527 dbus-cleanup-sockets, dbus-daemon, dbus-launch, dbus-monitor,
528 dbus-run-session, dbus-send, dbus-test-tool,
529 dbus-update-activation-environment, and dbus-uuidgen
530 </seg>
531 <seg>
532 libdbus-1.so
533 </seg>
534 <seg>
535 /etc/dbus-1,
536 /usr/{include,lib}/dbus-1.0,
537 /usr/share/dbus-1,
538 /usr/share/doc/dbus-&dbus-version;, and
539 /var/{lib,run}/dbus
540 </seg>
541 </seglistitem>
542 </segmentedlist>
543
544 <variablelist>
545 <bridgehead renderas="sect3">Short Descriptions</bridgehead>
546 <?dbfo list-presentation="list"?>
547 <?dbhtml list-presentation="table"?>
548
549 <varlistentry id="dbus-cleanup-sockets">
550 <term><command>dbus-cleanup-sockets</command></term>
551 <listitem>
552 <para>
553 is used to clean up leftover sockets in a directory.
554 </para>
555 <indexterm zone="dbus dbus-cleanup-sockets">
556 <primary sortas="b-dbus-cleanup-sockets">dbus-cleanup-sockets</primary>
557 </indexterm>
558 </listitem>
559 </varlistentry>
560
561 <varlistentry id="dbus-daemon">
562 <term><command>dbus-daemon</command></term>
563 <listitem>
564 <para>
565 is the <application>D-Bus</application> message bus daemon.
566 </para>
567 <indexterm zone="dbus dbus-daemon">
568 <primary sortas="b-dbus-daemon">dbus-daemon</primary>
569 </indexterm>
570 </listitem>
571 </varlistentry>
572
573 <varlistentry id="dbus-launch">
574 <term><command>dbus-launch</command></term>
575 <listitem>
576 <para>
577 is used to start <command>dbus-daemon</command> from a shell
578 script. It would normally be called from a user's login
579 scripts.
580 </para>
581 <indexterm zone="dbus dbus-launch">
582 <primary sortas="b-dbus-launch">dbus-launch</primary>
583 </indexterm>
584 </listitem>
585 </varlistentry>
586
587 <varlistentry id="dbus-monitor">
588 <term><command>dbus-monitor</command></term>
589 <listitem>
590 <para>
591 is used to monitor messages going through a
592 <application>D-Bus</application> message bus.
593 </para>
594 <indexterm zone="dbus dbus-monitor">
595 <primary sortas="b-dbus-monitor">dbus-monitor</primary>
596 </indexterm>
597 </listitem>
598 </varlistentry>
599
600 <varlistentry id="dbus-run-session">
601 <term><command>dbus-run-session</command></term>
602 <listitem>
603 <para>
604 start a process as a new <application>D-Bus</application> session.
605 </para>
606 <indexterm zone="dbus dbus-run-session">
607 <primary sortas="b-dbus-run-session">dbus-run-session</primary>
608 </indexterm>
609 </listitem>
610 </varlistentry>
611
612 <varlistentry id="dbus-send">
613 <term><command>dbus-send</command></term>
614 <listitem>
615 <para>
616 is used to send a message to a <application>D-Bus</application>
617 message bus.
618 </para>
619 <indexterm zone="dbus dbus-send">
620 <primary sortas="b-dbus-send">dbus-send</primary>
621 </indexterm>
622 </listitem>
623 </varlistentry>
624
625 <varlistentry id="dbus-test-tool">
626 <term><command>dbus-test-tool</command></term>
627 <listitem>
628 <para>
629 is a <application>D-Bus</application> traffic generator and test
630 tool; it is a multi-purpose tool for debugging and profiling
631 <application>D-Bus</application>.
632 </para>
633 <indexterm zone="dbus dbus-test-tool">
634 <primary sortas="b-dbus-test-tool">dbus-test-tool</primary>
635 </indexterm>
636 </listitem>
637 </varlistentry>
638
639 <varlistentry id="dbus-update-activation-environment">
640 <term><command>dbus-update-activation-environment</command></term>
641 <listitem>
642 <para>
643 is used to update the environment used for
644 <application>D-Bus</application> session services;
645 it updates the list of environment variables used by
646 <command>dbus-daemon --session</command> when it activates session
647 services without using systemd.
648 </para>
649 <indexterm zone="dbus dbus-update-activation-environment">
650 <primary sortas="b-dbus-update-activation-environment">
651 dbus-update-activation-environment</primary>
652 </indexterm>
653 </listitem>
654 </varlistentry>
655
656 <varlistentry id="dbus-uuidgen">
657 <term><command>dbus-uuidgen</command></term>
658 <listitem>
659 <para>
660 is used to generate a universally unique ID.
661 </para>
662 <indexterm zone="dbus dbus-uuidgen">
663 <primary sortas="b-dbus-uuidgen">dbus-uuidgen</primary>
664 </indexterm>
665 </listitem>
666 </varlistentry>
667
668 <varlistentry id="libdbus-1">
669 <term><filename class="libraryfile">libdbus-1.so</filename></term>
670 <listitem>
671 <para>
672 contains the API functions used by the
673 <application>D-Bus</application> message daemon.
674 <application>D-Bus</application> is first a library that provides
675 one-to-one communication between any two applications;
676 <command>dbus-daemon</command> is an application that uses this
677 library to implement a message bus daemon.
678 </para>
679 <indexterm zone="dbus libdbus-1">
680 <primary sortas="c-libdbus-1">libdbus-1.so</primary>
681 </indexterm>
682 </listitem>
683 </varlistentry>
684
685 </variablelist>
686
687 </sect2>
688
689 <sect2 role="content" revision="systemd">
690 <title>Contents</title>
691
692 <para>
693 A list of the installed files, along with their short
694 descriptions can be found at
695 <ulink url="&lfs-rootd;/chapter06/dbus.html#contents-dbus"/>.
696 </para>
697
698 </sect2>
699
700
701</sect1>
702
Note: See TracBrowser for help on using the repository browser.