| 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 "e809d7aa905ad82adeaf1d59db5445b1">
|
|---|
| 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.7 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 | -->
|
|---|
| 19 | ]>
|
|---|
| 20 |
|
|---|
| 21 | <sect1 id="dbus" xreflabel="dbus-&dbus-version;">
|
|---|
| 22 | <?dbhtml filename="dbus.html"?>
|
|---|
| 23 |
|
|---|
| 24 |
|
|---|
| 25 | <title>dbus-&dbus-version;</title>
|
|---|
| 26 |
|
|---|
| 27 | <indexterm zone="dbus">
|
|---|
| 28 | <primary sortas="a-D-Bus">D-Bus</primary>
|
|---|
| 29 | </indexterm>
|
|---|
| 30 |
|
|---|
| 31 | <sect2 role="package">
|
|---|
| 32 | <title>Introduction to D-Bus</title>
|
|---|
| 33 |
|
|---|
| 34 | <para revision="sysv">
|
|---|
| 35 | <application>D-Bus</application> is a message bus system, a simple way
|
|---|
| 36 | for applications to talk to one another.
|
|---|
| 37 | <application>D-Bus</application> supplies both a system daemon (for
|
|---|
| 38 | events such as <quote>new hardware device added</quote> or <quote>printer
|
|---|
| 39 | queue changed</quote>) and a per-user-login-session daemon (for general
|
|---|
| 40 | IPC needs among user applications). Also, the message bus is built on top
|
|---|
| 41 | of a general one-to-one message passing framework, which can be used by
|
|---|
| 42 | any two applications to communicate directly (without going through the
|
|---|
| 43 | message bus daemon).
|
|---|
| 44 | </para>
|
|---|
| 45 |
|
|---|
| 46 | <para revision="systemd">
|
|---|
| 47 | Even though <application>D-Bus</application> was built in LFS, there are
|
|---|
| 48 | some features provided by the package that other BLFS packages need, but
|
|---|
| 49 | their dependencies didn't fit into LFS.
|
|---|
| 50 | </para>
|
|---|
| 51 |
|
|---|
| 52 | &lfs113_checked;
|
|---|
| 53 |
|
|---|
| 54 | <bridgehead renderas="sect3">Package Information</bridgehead>
|
|---|
| 55 | <itemizedlist spacing="compact">
|
|---|
| 56 | <listitem>
|
|---|
| 57 | <para>
|
|---|
| 58 | Download (HTTP): <ulink url="&dbus-download-http;"/>
|
|---|
| 59 | </para>
|
|---|
| 60 | </listitem>
|
|---|
| 61 | <listitem>
|
|---|
| 62 | <para>
|
|---|
| 63 | Download (FTP): <ulink url="&dbus-download-ftp;"/>
|
|---|
| 64 | </para>
|
|---|
| 65 | </listitem>
|
|---|
| 66 | <listitem>
|
|---|
| 67 | <para>
|
|---|
| 68 | Download MD5 sum: &dbus-md5sum;
|
|---|
| 69 | </para>
|
|---|
| 70 | </listitem>
|
|---|
| 71 | <listitem>
|
|---|
| 72 | <para>
|
|---|
| 73 | Download size: &dbus-size;
|
|---|
| 74 | </para>
|
|---|
| 75 | </listitem>
|
|---|
| 76 | <listitem>
|
|---|
| 77 | <para>
|
|---|
| 78 | Estimated disk space required: &dbus-buildsize;
|
|---|
| 79 | </para>
|
|---|
| 80 | </listitem>
|
|---|
| 81 | <listitem>
|
|---|
| 82 | <para>
|
|---|
| 83 | Estimated build time: &dbus-time;
|
|---|
| 84 | </para>
|
|---|
| 85 | </listitem>
|
|---|
| 86 | </itemizedlist>
|
|---|
| 87 |
|
|---|
| 88 | <bridgehead renderas="sect3">D-Bus Dependencies</bridgehead>
|
|---|
| 89 |
|
|---|
| 90 | <bridgehead renderas="sect4" revision="systemd">Required</bridgehead>
|
|---|
| 91 | <para role="required" revision="systemd">
|
|---|
| 92 | <xref linkend="systemd"/>
|
|---|
| 93 | </para>
|
|---|
| 94 |
|
|---|
| 95 |
|
|---|
| 96 | <bridgehead renderas="sect4">Recommended</bridgehead>
|
|---|
| 97 | <para role="recommended">
|
|---|
| 98 | <xref linkend="xorg7-lib"/> (for <command>dbus-launch</command> program)
|
|---|
| 99 | <phrase revision="sysv">and <xref linkend="elogind"/> (These are
|
|---|
| 100 | circular dependencies. First build without them, and then again after
|
|---|
| 101 | both packages are installed.)</phrase>
|
|---|
| 102 | </para>
|
|---|
| 103 |
|
|---|
| 104 | <bridgehead renderas="sect4">Optional</bridgehead>
|
|---|
| 105 | <para role="optional">
|
|---|
| 106 | For the tests:
|
|---|
| 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="&gnome-download-http;/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 &&
|
|---|
| 134 | useradd -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 | --runstatedir=/run \
|
|---|
| 149 | --enable-user-session \
|
|---|
| 150 | --disable-doxygen-docs \
|
|---|
| 151 | --disable-xml-docs \
|
|---|
| 152 | --disable-static \
|
|---|
| 153 | --with-systemduserunitdir=no \
|
|---|
| 154 | --with-systemdsystemunitdir=no \
|
|---|
| 155 | --docdir=/usr/share/doc/dbus-&dbus-version; \
|
|---|
| 156 | --with-system-socket=/run/dbus/system_bus_socket &&
|
|---|
| 157 | make</userinput></screen>
|
|---|
| 158 |
|
|---|
| 159 | <screen revision="systemd"><userinput>./configure --prefix=/usr \
|
|---|
| 160 | --sysconfdir=/etc \
|
|---|
| 161 | --localstatedir=/var \
|
|---|
| 162 | --runstatedir=/run \
|
|---|
| 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-system-socket=/run/dbus/system_bus_socket &&
|
|---|
| 169 | make</userinput></screen>
|
|---|
| 170 |
|
|---|
| 171 | <para>
|
|---|
| 172 | See below for test instructions.
|
|---|
| 173 | </para>
|
|---|
| 174 |
|
|---|
| 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 |
|
|---|
| 192 | <para>
|
|---|
| 193 | Now, as the <systemitem class="username">root</systemitem> user:
|
|---|
| 194 | </para>
|
|---|
| 195 |
|
|---|
| 196 | <screen role="root"><userinput>make install</userinput></screen>
|
|---|
| 197 |
|
|---|
| 198 | <!-- FIXME: No longer needed with usr merge
|
|---|
| 199 | <para>
|
|---|
| 200 | The shared library needs to be moved to
|
|---|
| 201 | <filename class="directory">/lib</filename>, and as a result the
|
|---|
| 202 | <filename class="extension">.so</filename> file in
|
|---|
| 203 | <filename class="directory">/usr/lib</filename> will need to be
|
|---|
| 204 | recreated. Run the following command as the
|
|---|
| 205 | <systemitem class="username">root</systemitem> user:
|
|---|
| 206 | </para>
|
|---|
| 207 |
|
|---|
| 208 | <screen role="root"><userinput>mv -v /usr/lib/libdbus-1.so.* /lib &&
|
|---|
| 209 | ln -sfv ../../lib/$(readlink /usr/lib/libdbus-1.so) /usr/lib/libdbus-1.so</userinput></screen>
|
|---|
| 210 | -->
|
|---|
| 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 &&
|
|---|
| 220 | chmod -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 -sfv /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
|
|---|
| 248 | systemctl start multi-user.target</userinput></screen>
|
|---|
| 249 | -->
|
|---|
| 250 |
|
|---|
| 251 | <para>
|
|---|
| 252 | The dbus tests cannot be run until after <xref linkend="dbus-python"/>
|
|---|
| 253 | and <xref linkend="pygobject3"/> have
|
|---|
| 254 | been installed. They must be run as an unprivileged user from a local
|
|---|
| 255 | session with bus address. To run the standard tests issue
|
|---|
| 256 | <command>make check</command>.
|
|---|
| 257 | </para>
|
|---|
| 258 |
|
|---|
| 259 | <para>
|
|---|
| 260 | If you want to run the unit regression tests, configure requires
|
|---|
| 261 | additional parameters which expose additional functionality in the
|
|---|
| 262 | binaries that are not intended to be used in a production build of
|
|---|
| 263 | <application>D-Bus</application>. If you would like to run the tests,
|
|---|
| 264 | issue the following commands (for the tests, you don't need to build the
|
|---|
| 265 | docs):
|
|---|
| 266 | </para>
|
|---|
| 267 |
|
|---|
| 268 | <screen remap="test"><userinput>make distclean &&
|
|---|
| 269 | PYTHON=python3 ./configure --enable-tests \
|
|---|
| 270 | --enable-asserts \
|
|---|
| 271 | --disable-doxygen-docs \
|
|---|
| 272 | --disable-xml-docs &&
|
|---|
| 273 | make &&
|
|---|
| 274 | make check</userinput></screen>
|
|---|
| 275 |
|
|---|
| 276 | <para>
|
|---|
| 277 | There have been reports 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>
|
|---|
| 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 |
|
|---|
| 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>: Builds 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>: Builds 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>: Enables 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 > /etc/dbus-1/session-local.conf << "EOF"
|
|---|
| 398 | <literal><!DOCTYPE busconfig PUBLIC
|
|---|
| 399 | "-//freedesktop//DTD D-BUS Bus Configuration 1.0//EN"
|
|---|
| 400 | "http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd">
|
|---|
| 401 | <busconfig>
|
|---|
| 402 |
|
|---|
| 403 | <!-- Search for .service files in /usr/local -->
|
|---|
| 404 | <servicedir>/usr/local/share/dbus-1/services</servicedir>
|
|---|
| 405 |
|
|---|
| 406 | </busconfig></literal>
|
|---|
| 407 | EOF</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>gdm</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-x11</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
|
|---|
| 477 | eval `dbus-launch`
|
|---|
| 478 | export 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
|
|---|
| 487 | kill $DBUS_SESSION_BUS_PID</literal></userinput></screen>
|
|---|
| 488 | </listitem>
|
|---|
| 489 |
|
|---|
| 490 | <!-- KDM is no longer usable, SDDM is it's replacement
|
|---|
| 491 | <listitem>
|
|---|
| 492 | <para>
|
|---|
| 493 | A hint has been written that provides ways to start scripts
|
|---|
| 494 | using the KDM session manager of KDE. The concepts in this hint could
|
|---|
| 495 | possibly be used with other session managers as well. The hint is
|
|---|
| 496 | located at <ulink
|
|---|
| 497 | url="&hints-root;/downloads/files/execute-session-scripts-using-kdm.txt"/>.
|
|---|
| 498 | </para>
|
|---|
| 499 | </listitem>
|
|---|
| 500 | -->
|
|---|
| 501 |
|
|---|
| 502 | </itemizedlist>
|
|---|
| 503 |
|
|---|
| 504 | </sect3>
|
|---|
| 505 |
|
|---|
| 506 | </sect2>
|
|---|
| 507 |
|
|---|
| 508 | <sect2 role="content" revision="sysv">
|
|---|
| 509 | <title>Contents</title>
|
|---|
| 510 |
|
|---|
| 511 | <segmentedlist>
|
|---|
| 512 | <segtitle>Installed Programs</segtitle>
|
|---|
| 513 | <segtitle>Installed Library</segtitle>
|
|---|
| 514 | <segtitle>Installed Directories</segtitle>
|
|---|
| 515 |
|
|---|
| 516 | <seglistitem>
|
|---|
| 517 | <seg>
|
|---|
| 518 | dbus-cleanup-sockets, dbus-daemon, dbus-launch, dbus-monitor,
|
|---|
| 519 | dbus-run-session, dbus-send, dbus-test-tool,
|
|---|
| 520 | dbus-update-activation-environment, and dbus-uuidgen
|
|---|
| 521 | </seg>
|
|---|
| 522 | <seg>
|
|---|
| 523 | libdbus-1.so
|
|---|
| 524 | </seg>
|
|---|
| 525 | <seg>
|
|---|
| 526 | /etc/dbus-1,
|
|---|
| 527 | /usr/{include,lib}/dbus-1.0,
|
|---|
| 528 | /usr/lib/cmake/DBus1,
|
|---|
| 529 | /usr/share/dbus-1,
|
|---|
| 530 | /usr/share/xml/dbus-1,
|
|---|
| 531 | /usr/share/doc/dbus-&dbus-version;, and
|
|---|
| 532 | /var/{lib,run}/dbus
|
|---|
| 533 | </seg>
|
|---|
| 534 | </seglistitem>
|
|---|
| 535 | </segmentedlist>
|
|---|
| 536 |
|
|---|
| 537 | <variablelist>
|
|---|
| 538 | <bridgehead renderas="sect3">Short Descriptions</bridgehead>
|
|---|
| 539 | <?dbfo list-presentation="list"?>
|
|---|
| 540 | <?dbhtml list-presentation="table"?>
|
|---|
| 541 |
|
|---|
| 542 | <varlistentry id="dbus-cleanup-sockets">
|
|---|
| 543 | <term><command>dbus-cleanup-sockets</command></term>
|
|---|
| 544 | <listitem>
|
|---|
| 545 | <para>
|
|---|
| 546 | is used to clean up leftover sockets in a directory
|
|---|
| 547 | </para>
|
|---|
| 548 | <indexterm zone="dbus dbus-cleanup-sockets">
|
|---|
| 549 | <primary sortas="b-dbus-cleanup-sockets">dbus-cleanup-sockets</primary>
|
|---|
| 550 | </indexterm>
|
|---|
| 551 | </listitem>
|
|---|
| 552 | </varlistentry>
|
|---|
| 553 |
|
|---|
| 554 | <varlistentry id="dbus-daemon">
|
|---|
| 555 | <term><command>dbus-daemon</command></term>
|
|---|
| 556 | <listitem>
|
|---|
| 557 | <para>
|
|---|
| 558 | is the <application>D-Bus</application> message bus daemon
|
|---|
| 559 | </para>
|
|---|
| 560 | <indexterm zone="dbus dbus-daemon">
|
|---|
| 561 | <primary sortas="b-dbus-daemon">dbus-daemon</primary>
|
|---|
| 562 | </indexterm>
|
|---|
| 563 | </listitem>
|
|---|
| 564 | </varlistentry>
|
|---|
| 565 |
|
|---|
| 566 | <varlistentry id="dbus-launch">
|
|---|
| 567 | <term><command>dbus-launch</command></term>
|
|---|
| 568 | <listitem>
|
|---|
| 569 | <para>
|
|---|
| 570 | is used to start <command>dbus-daemon</command> from a shell
|
|---|
| 571 | script. It would normally be called from a user's login
|
|---|
| 572 | scripts
|
|---|
| 573 | </para>
|
|---|
| 574 | <indexterm zone="dbus dbus-launch">
|
|---|
| 575 | <primary sortas="b-dbus-launch">dbus-launch</primary>
|
|---|
| 576 | </indexterm>
|
|---|
| 577 | </listitem>
|
|---|
| 578 | </varlistentry>
|
|---|
| 579 |
|
|---|
| 580 | <varlistentry id="dbus-monitor">
|
|---|
| 581 | <term><command>dbus-monitor</command></term>
|
|---|
| 582 | <listitem>
|
|---|
| 583 | <para>
|
|---|
| 584 | is used to monitor messages going through a
|
|---|
| 585 | <application>D-Bus</application> message bus
|
|---|
| 586 | </para>
|
|---|
| 587 | <indexterm zone="dbus dbus-monitor">
|
|---|
| 588 | <primary sortas="b-dbus-monitor">dbus-monitor</primary>
|
|---|
| 589 | </indexterm>
|
|---|
| 590 | </listitem>
|
|---|
| 591 | </varlistentry>
|
|---|
| 592 |
|
|---|
| 593 | <varlistentry id="dbus-run-session">
|
|---|
| 594 | <term><command>dbus-run-session</command></term>
|
|---|
| 595 | <listitem>
|
|---|
| 596 | <para>
|
|---|
| 597 | starts a process as a new <application>D-Bus</application> session
|
|---|
| 598 | </para>
|
|---|
| 599 | <indexterm zone="dbus dbus-run-session">
|
|---|
| 600 | <primary sortas="b-dbus-run-session">dbus-run-session</primary>
|
|---|
| 601 | </indexterm>
|
|---|
| 602 | </listitem>
|
|---|
| 603 | </varlistentry>
|
|---|
| 604 |
|
|---|
| 605 | <varlistentry id="dbus-send">
|
|---|
| 606 | <term><command>dbus-send</command></term>
|
|---|
| 607 | <listitem>
|
|---|
| 608 | <para>
|
|---|
| 609 | is used to send a message to a <application>D-Bus</application>
|
|---|
| 610 | message bus
|
|---|
| 611 | </para>
|
|---|
| 612 | <indexterm zone="dbus dbus-send">
|
|---|
| 613 | <primary sortas="b-dbus-send">dbus-send</primary>
|
|---|
| 614 | </indexterm>
|
|---|
| 615 | </listitem>
|
|---|
| 616 | </varlistentry>
|
|---|
| 617 |
|
|---|
| 618 | <varlistentry id="dbus-test-tool">
|
|---|
| 619 | <term><command>dbus-test-tool</command></term>
|
|---|
| 620 | <listitem>
|
|---|
| 621 | <para>
|
|---|
| 622 | is a <application>D-Bus</application> traffic generator and test
|
|---|
| 623 | tool; it is a multi-purpose tool for debugging and profiling
|
|---|
| 624 | <application>D-Bus</application>
|
|---|
| 625 | </para>
|
|---|
| 626 | <indexterm zone="dbus dbus-test-tool">
|
|---|
| 627 | <primary sortas="b-dbus-test-tool">dbus-test-tool</primary>
|
|---|
| 628 | </indexterm>
|
|---|
| 629 | </listitem>
|
|---|
| 630 | </varlistentry>
|
|---|
| 631 |
|
|---|
| 632 | <varlistentry id="dbus-update-activation-environment">
|
|---|
| 633 | <term><command>dbus-update-activation-environment</command></term>
|
|---|
| 634 | <listitem>
|
|---|
| 635 | <para>
|
|---|
| 636 | is used to update the environment used for
|
|---|
| 637 | <application>D-Bus</application> session services;
|
|---|
| 638 | it updates the list of environment variables used by
|
|---|
| 639 | <command>dbus-daemon --session</command> when it activates session
|
|---|
| 640 | services without using systemd
|
|---|
| 641 | </para>
|
|---|
| 642 | <indexterm zone="dbus dbus-update-activation-environment">
|
|---|
| 643 | <primary sortas="b-dbus-update-activation-environment">
|
|---|
| 644 | dbus-update-activation-environment</primary>
|
|---|
| 645 | </indexterm>
|
|---|
| 646 | </listitem>
|
|---|
| 647 | </varlistentry>
|
|---|
| 648 |
|
|---|
| 649 | <varlistentry id="dbus-uuidgen">
|
|---|
| 650 | <term><command>dbus-uuidgen</command></term>
|
|---|
| 651 | <listitem>
|
|---|
| 652 | <para>
|
|---|
| 653 | is used to generate a universally unique ID
|
|---|
| 654 | </para>
|
|---|
| 655 | <indexterm zone="dbus dbus-uuidgen">
|
|---|
| 656 | <primary sortas="b-dbus-uuidgen">dbus-uuidgen</primary>
|
|---|
| 657 | </indexterm>
|
|---|
| 658 | </listitem>
|
|---|
| 659 | </varlistentry>
|
|---|
| 660 |
|
|---|
| 661 | <varlistentry id="libdbus-1">
|
|---|
| 662 | <term><filename class="libraryfile">libdbus-1.so</filename></term>
|
|---|
| 663 | <listitem>
|
|---|
| 664 | <para>
|
|---|
| 665 | contains the API functions used by the
|
|---|
| 666 | <application>D-Bus</application> message daemon.
|
|---|
| 667 | <application>D-Bus</application> is first a library that provides
|
|---|
| 668 | one-to-one communication between any two applications;
|
|---|
| 669 | <command>dbus-daemon</command> is an application that uses this
|
|---|
| 670 | library to implement a message bus daemon
|
|---|
| 671 | </para>
|
|---|
| 672 | <indexterm zone="dbus libdbus-1">
|
|---|
| 673 | <primary sortas="c-libdbus-1">libdbus-1.so</primary>
|
|---|
| 674 | </indexterm>
|
|---|
| 675 | </listitem>
|
|---|
| 676 | </varlistentry>
|
|---|
| 677 |
|
|---|
| 678 | </variablelist>
|
|---|
| 679 |
|
|---|
| 680 | </sect2>
|
|---|
| 681 |
|
|---|
| 682 | <sect2 role="content" revision="systemd">
|
|---|
| 683 | <title>Contents</title>
|
|---|
| 684 |
|
|---|
| 685 | <para>
|
|---|
| 686 | A list of the installed files, along with their short
|
|---|
| 687 | descriptions can be found at
|
|---|
| 688 | <ulink url="&lfs-root;/chapter08/dbus.html#contents-dbus"/>.
|
|---|
| 689 | </para>
|
|---|
| 690 |
|
|---|
| 691 | </sect2>
|
|---|
| 692 |
|
|---|
| 693 | </sect1>
|
|---|
