source: general/sysutils/dbus.xml@ 42ddc30

12.0 12.1 kea ken/TL2024 ken/tuningfonts lazarus lxqt plabs/newcss python3.11 rahul/power-profiles-daemon renodr/vulkan-addition trunk xry111/llvm18 xry111/xf86-video-removal
Last change on this file since 42ddc30 was 42ddc30, checked in by Xi Ruoyao <xry111@…>, 11 months ago

treewide: Replace "User Notes" with "Editor Notes"

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