source: general/sysutils/dbus.xml@ a761478

10.0 10.1 11.0 11.1 11.2 11.3 12.0 12.1 12.2 gimp3 kea ken/TL2024 ken/inkscape-core-mods ken/tuningfonts lazarus lxqt plabs/newcss plabs/python-mods python3.11 qt5new rahul/power-profiles-daemon renodr/vulkan-addition trunk upgradedb xry111/for-12.3 xry111/intltool xry111/llvm18 xry111/soup3 xry111/spidermonkey128 xry111/test-20220226 xry111/xf86-video-removal
Last change on this file since a761478 was a761478, checked in by Douglas R. Reno <renodr@…>, 5 years ago

Remove the systemctl instructions from systemd and dbus.
Update to EOG-3.36.1
Update to Evince-3.36.0
Update to evolution-3.36.1
Update to file-roller-3.36.1
Update to gnome-calculator-3.36.0
Update to gnome-disk-utility-3.36.1
Update to gnome-maps-3.36.1
Update to gnome-screenshot-3.36.0
Update to gnome-system-monitor-3.36.0
Update to gnome-terminal-3.36.1.1

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