source: general/sysutils/dbus.xml@ 51dfb3e

10.0 10.1 11.0 9.0 9.1 ken/refactor-virt lazarus qt5new trunk xry111/git-date xry111/git-date-for-trunk xry111/git-date-test
Last change on this file since 51dfb3e was 51dfb3e, checked in by Bruce Dubbs <bdubbs@…>, 2 years ago

Move BLFS/trunk/BOOK and BLFS/trunk/bootscripts to
BLFS/branches/old-trunk-20190627 and BLFS/branches/old-bootscripts-20190627.

Move BLFS/branches/elogind-book and BLFS/branches/elogind-bootscripts
to trunk.

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

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