1N/A<!
DOCTYPE REFENTRY PUBLIC "-//Sun Microsystems//DTD DocBook V3.0-Based SolBook Subset V2.0//EN" [
1N/A<!--ArborText, Inc., 1988-1999, v.4002-->
1N/A<!--ARC : LSARC 2006/368 D-BUS Message Bus System --> 1N/A<!
ENTITY cmd "dbus-daemon">
1N/A<!
ENTITY suncopy "Copyright (c) 2007,2009 Sun Microsystems, Inc. All Rights Reserved.">
1N/A<
refentry id="dbus-daemon-1">
1N/A<!-- %Z%%M% %I% %E% SMI; --> 1N/A<
refmeta><
refentrytitle>&cmd;</
refentrytitle><
manvolnum>3</
manvolnum>
1N/A<
refmiscinfo class="date">25 Feb 2009</
refmiscinfo>
1N/A<
refmiscinfo class="sectdesc">&man3;</
refmiscinfo>
1N/A<
refmiscinfo class="software">&release;</
refmiscinfo>
1N/A<
refmiscinfo class="arch">generic</
refmiscinfo>
1N/A<
refmiscinfo class="copyright">&suncopy;</
refmiscinfo>
1N/A<
indexterm><
primary>&cmd;</
primary></
indexterm><
indexterm><
primary>
1N/A</
primary></
indexterm><
refnamediv id="dbus-daemon-1-name">
1N/A<
refname>&cmd;</
refname><
refpurpose>
1N/A</
refpurpose></
refnamediv>
1N/A<
refsynopsisdiv id="dbus-daemon-1-synp"><
title>&synp-tt;</
title>
1N/A<
cmdsynopsis><
command>&cmd;</
command>
1N/A<
arg choice="opt"><
option>-config-file=<
replaceable>file</
replaceable></
option></
arg>
1N/A<
arg choice="opt"><
option>-fork</
option> | <
option>-nofork</
option></
arg>
1N/A<
arg choice="opt"><
option>-introspect</
option></
arg>
1N/A<
arg choice="opt"><
option>-print-address[=<
replaceable>descriptor</
replaceable>]</
option></
arg>
1N/A<
arg choice="opt"><
option>-print-pid[=<
replaceable>descriptor</
replaceable>]</
option></
arg>
1N/A<
arg choice="opt"><
option>-session</
option></
arg>
1N/A<
arg choice="opt"><
option>-system</
option></
arg>
1N/A<
arg choice="opt"><
option>-version</
option></
arg>
1N/A</
cmdsynopsis></
refsynopsisdiv>
1N/A<
refsect1 id="dbus-daemon-1-desc"><
title>&desc-tt;</
title>
1N/A<
command>&cmd;</
command> is the D\-Bus message bus daemon. D\-Bus is first a
1N/Alibrary that provides one\-to\-one communication between any two applications;
1N/A<
command>&cmd;</
command> is an application that uses this library to implement
1N/Aa message bus daemon. Multiple programs connect to the message bus daemon and
1N/Acan exchange messages with one another.
1N/AThere are two standard message bus instances. <
command>&cmd;</
command> is used
1N/Afor both of these instances, but with a different configuration file.
1N/Asystemwide message bus - Launched when the system is started and is enabled by
1N/Adefault. Additional systemwide services can be launched via D\-Bus
1N/A"service activation" However, "service activation" is
1N/Adisabled on Solaris. Note that the <
option>-system</
option> option is
1N/Aper-user-login-session message bus - Launched each time a user logs in. Note
1N/Athat the <
option>-session</
option> option is equivalent to:
1N/ABy creating additional configuration files and using the
1N/A<
option>-config\-file</
option> option, additional special-purpose message bus
1N/Adaemons could be created.
1N/AOn Solaris, D\-Bus is configured with "service activation" disabled,
1N/Aso that users cannot launch systemwide bus services on demand. This feature is
1N/Anot used by any applications that are currently shipped with Solaris.
1N/AOn Solaris, the D\-Bus service is managed by the
1N/A<
citerefentry><
refentrytitle>smf</
refentrytitle>
1N/A<
manvolnum>5</
manvolnum></
citerefentry>
1N/Aservice management facility under the service identifier
1N/AOn Solaris, it is recommended that you use the
1N/A<
citerefentry><
refentrytitle>svcadm</
refentrytitle>
1N/A<
manvolnum>1m</
manvolnum></
citerefentry> utility to start and stop the D\-Bus
1N/AThe systemwide daemon is largely used for broadcasting system events, such as
1N/AThe per-session daemon is used for various interprocess communication among
1N/Adesktop applications (however, it is not tied to X or the GUI in any way).
1N/ASIGHUP will cause the D\-Bus daemon to PARTIALLY reload its configuration file
1N/Aand to flush its
user/
group information caches. Some configuration changes
1N/Awould require kicking all applications off the bus; so they will only take
1N/Aeffect if you restart the daemon. Policy changes should take effect with
1N/A<
refsect1 id="dbus-daemon-1-opts"><
title>&opts-tt;</
title>
The following options are supported:
<
variablelist termlength="wholeline">
<
term><
option>-config-file=<
replaceable>file</
replaceable></
option></
term>
Use the given configuration <
replaceable>file</
replaceable>.
</
listitem></
varlistentry>
<
term><
option>-fork</
option></
term>
Force the message bus to fork and become a daemon, regardless of configuration
</
listitem></
varlistentry>
<
term><
option>-introspect</
option></
term>
Print introspect data and exit.
</
listitem></
varlistentry>
<
term><
option>-nofork</
option></
term>
Avoid running the message bus as a daemon, regardless of configuration file
</
listitem></
varlistentry>
<
term><
option>-print-address[=<
replaceable>descriptor</
replaceable>]</
option></
term>
Print the address of the message bus to standard output, or to the given file
<
replaceable>descriptor</
replaceable>. This is used by programs that launch
</
listitem></
varlistentry>
<
term><
option>-print-pid[=<
replaceable>descriptor</
replaceable>]</
option></
term>
Print the process ID of the message bus to standard output, or to the given
file <
replaceable>descriptor</
replaceable>. This is used by programs that
</
listitem></
varlistentry>
<
term><
option>-session</
option></
term>
Use the standard configuration file for the per-login-session message bus.
</
listitem></
varlistentry>
<
term><
option>-system</
option></
term>
Use the standard configuration file for the systemwide message bus.
</
listitem></
varlistentry>
<
term><
option>-version</
option></
term>
Print the version of the daemon.
</
listitem></
varlistentry>
</
variablelist></
refsect1>
<
refsect1 id="dbus-daemon-1-envr"><
title>&envr-tt;</
title>
<
citerefentry><
refentrytitle>environ</
refentrytitle>
<
manvolnum>5</
manvolnum></
citerefentry>
for descriptions of the following environment variables:
<
variablelist termlength="wholeline">
<
term>DBUS_SESSION_BUS_ADDRESS</
term>
The address of the login session message bus. If this variable is not set,
applications may also try to read the address from the X Window System root
window property _DBUS_SESSION_BUS_ADDRESS. The root window property
must have type STRING. The environment variable should have precedence over
the root window property.
</
listitem></
varlistentry>
<
term>DBUS_STARTER_BUS_TYPE</
term>
If the well-known type of the message bus is "session", then
this environment variable will be set to "session". If the
type of the message bus is "system;", then this environment
variable will be set to "system".
</
listitem></
varlistentry>
<
term>DBUS_VERBOSE</
term>
Set DBUS_VERSION=1 to enable debugging, if D\-Bus was compiled with verbose
</
listitem></
varlistentry>
</
variablelist></
refsect1>
<
refsect1 id="dbus-daemon-1-exit"><
title>&exit-tt;</
title>
<
para>The following exit values are returned:</
para>
<
variablelist termlength="xtranarrow">
<
term><
returnvalue>0</
returnvalue></
term>
Application exited successfully
</
listitem></
varlistentry>
<
term><
returnvalue>>0</
returnvalue></
term>
Application exited with failure
</
listitem></
varlistentry>
</
variablelist></
refsect1>
<
refsect1 id="dbus-daemon-1-exde"><
title>&exde-tt;</
title>
<
title>CONFIGURATION FILE</
title>
A message bus daemon has a configuration file that specializes it for a
particular application. For example, one configuration file might set up the
message bus to be a systemwide message bus, while another might set it
up to be a per-user-login-session bus.
The configuration file also establishes resource limits, security parameters,
The configuration file is not part of any interoperability specification and
its backward compatibility is not guaranteed; this document is documentation,
The standard systemwide and per-session message bus setups are configured in
files to avoid modifying the primary configuration files.
The configuration file is an XML document. It must have the following doctype
<!DOCTYPE busconfig PUBLIC "-//freedesktop//DTD D\-Bus Bus Configuration 1.0//EN"
The following elements may be present in the configuration file.
The well-known type of the message bus. Currently known values are
"system" and "session"; if other values are set, they
should be either added to the D\-Bus specification, or namespaced. The last
<type> element "wins" (previous values are ignored). This
element only controls which message bus specific environment variables are set
in activated clients. Most of the policy that distinguishes a session bus from
the system bus is controlled from the other elements in the configuration file.
If the well-known type of the message bus is "session", then the
DBUS_STARTER_BUS_TYPE environment variable will be set to "session"
and the DBUS_SESSION_BUS_ADDRESS environment variable will be set to the
address of the session bus. Likewise, if the type of the message bus is
"system", then the DBUS_STARTER_BUS_TYPE environment variable will be
set to "system" and the DBUS_SESSION_BUS_ADDRESS environment variable
will be set to the address of the system bus (which is normally well known
Example: <type>session</type>
Include a file <include>
filename.conf</include> at this point. If
the filename is relative, it is located relative to the configuration file
<include> has an optional attribute "ignore_missing=(yes|no)"
which defaults to "no" if not provided. This attribute controls
whether it is a fatal error for the included file to be absent.
Include all files in <includedir>
foo.d</includedir> at this point.
Files in the directory are included in undefined order. Only files ending in
".conf" are included.
This is intended to allow extension of the system bus by particular packages.
For example, if CUPS wants to be able to send out notification of printer queue
applications to receive this message and allowed the printer daemon user to
The user account the daemon should run as, specified as either a username or a
UID. If the daemon cannot change to this UID on startup, it will exit. If
this element is not present, the daemon will not change or care about its UID.
The last <user> entry in the file "wins", the others are
The user is changed after the bus has completed initialization. So sockets,
etc. will be created before changing user, but no data will be read from
clients before changing user. This means that sockets and PID files can be
created in a location that requires root privileges for writing.
If present, the bus daemon becomes a real daemon (forks into the background,
etc.). This is generally used rather than the <
option>-fork</
option> command
If present, the bus daemon keeps its original umask when forking. This may be
useful to avoid affecting the behavior of child processes.
Add an address that the bus should listen on. The address is in the standard
Example: <listen>unix:path=/
tmp/
foo</listen>
Example: <listen>tcp:host=localhost,port=1234</listen>
If there are multiple <listen> elements, then the bus listens on multiple
addresses. The bus will pass its address to started services or other
interested parties with the last address given in <listen> first. That
is, applications will try to connect to the last <listen> address first.
tcp sockets can accept IPv4 addresses, IPv6 addresses or hostnames. If a
hostname resolves to multiple addresses, the server will bind to all of them.
The family=ipv4 or family=ipv6 options can be used to force it to bind to a
<listen>tcp:host=localhost,port=0,family=ipv4</listen>
A special case is using a port number of zero (or omitting the port), which
means to choose an available port selected by the operating system. The port
number chosen can be obtained with the <
option>-print-address</
option> command
line parameter and will be present in other cases where the server reports its
own address, such as when DBUS_SESSION_BUS_ADDRESS is set.
Example: <listen>tcp:host=localhost,port=0</listen>
tcp addresses also allow a bind=hostname option, which will override the host
option specifying what address to bind to, without changing the address
reported by the bus. The bind option can also take a special name '*' to
cause the bus to listen on all local address (INADDR_ANY). The specified host
should be a valid name of the local machine or weird stuff will happen.
Example: <listen>tcp:host=localhost,bind=*,port=0</listen>
Lists permitted authorization mechanisms. If this element does not exist, then
all known mechanisms are allowed. If there are multiple <auth> elements,
all the listed mechanisms are allowed. The order in which mechanisms are
listed is not meaningful.
Example: <auth>EXTERNAL</auth>
Example: <auth>DBUS_COOKIE_SHA1</auth>
Adds a directory to scan for <
filename>.service</
filename> files. Directories
are scanned starting with the last to appear in the config file (the first
<
filename>.service</
filename> file found that provides a particular service
Service files tell the bus how to automatically start a program. They are
primarily used with the per-user-session bus, not the systemwide bus.
<standard session servicedirs/>
<standard_session_servicedirs/> is equivalent to specifying a series of
<servicedir/> elements for each of the data directories in the "XDG
Base Directory Specification" with the subdirectory
The "XDG Base Directory Specification" should be found at
The <standard_session_servicedirs/> option is only relevant to the
per-user-session bus daemon defined in
configuration file would probably be nonsense.
<standard system servicedirs/>
<standard_system_servicedirs/> specifies the standard systemwide
activation directories that should be searched for service files. This option
The <standard_system_servicedirs/> option is only relevant
to the per-system bus daemon defined in
configuration file would probably be nonsense.
<servicehelper/> specifies the setuid helper that is used to launch
system daemons with an alternate user. Typically this would be the
<
command>dbus-daemon-launch-helper</
command> executable. Because
D\-Bus "service activation" is disabled on Solaris, the
<
command>dbus-daemon-launch-helper</
command> executable is not distributed
The <servicehelper/> option is only relevant to the per-system bus
any other configuration file would probably be nonsense.
<limit> establishes a resource limit. For example:
<limit name="max_message_size">64</limit>
<limit name="max_completed_connections">512</limit>
The name attribute is mandatory. Available limit names are:
"max_incoming_bytes" : total size in bytes of
"max_outgoing_bytes" : total size in bytes of
"max_message_size" : maximum size of a
"service_start_timeout" : milliseconds
"auth_timeout" : milliseconds
"max_completed_connections" : maximum number of
"max_incomplete_connections" : maximum number of
"max_connections_per_user" : maximum number of
"max_pending_service_starts" : maximum number of
"max_names_per_connection" : maximum number of
"max_match_rules_per_connection" : maximum number of
"max_replies_per_connection" : maximum number of
"reply_timeout" : milliseconds
one byte remains below the maximum. So you can in fact exceed the maximum by
max_completed_connections divided by max_connections_per_user is the number of
users that can work together to denial-of-service all other users by using up
all connections on the systemwide bus.
Limits are normally only of interest on the systemwide bus, not the user
The <policy> element defines a security policy to be applied to a
particular set of connections to the bus. A policy is made up of <allow>
and <deny> elements. Policies are normally used with the systemwide bus;
they are analogous to a firewall in that they allow expected traffic and
prevent unexpected traffic.
Currently, the system bus has a default-deny policy for sending method calls
and owning bus names. Everything else, in particular reply messages, receive
checks, and signals has a default allow policy.
In general, it is best to keep system services as small, targeted programs
which run in their own process and provide a single bus name. Then, all that
is needed is an <allow> rule for the "own" permission to let
the process claim the bus name, and a "send_destination" rule to
allow traffic from some or all uids to your service.
The <policy> element has one of four attributes:
context="(default|mandatory)"
at_console="(true|false)"
user="username or userid"
group="group name or gid"
Policies are applied to a connection as follows:
all context="default" policies are applied
all group="connection's user's group" policies are applied
all user="connection's auth user" policies are applied
all at_console="true" policies are applied
all at_console="false" policies are applied
all context="mandatory" policies are applied
Policies applied later will override those applied earlier, when the policies
order they appear in the config file.
<deny> and <allow>
A <deny> element appears below a <policy> element and prohibits
some action. The <allow> element makes an exception to previous
<deny> statements, and works just like <deny> but with the inverse
The possible attributes of these elements are:
send_interface="interface_name"
send_member="method_or_signal_name"
send_error="error_name"
send_destination="name"
send_type="method_call" | "method_return" | "signal" | "error"
receive_interface="interface_name"
receive_member="method_or_signal_name"
receive_error="error_name"
receive_sender="name"
receive_type="method_call" | "method_return" | "signal" | "error"
send_requested_reply="true" | "false"
receive_requested_reply="true" | "false"
eavesdrop="true" | "false"
user="username"
group="groupname"
<deny receive_interface="
org.
freedesktop.
System" receive_member="Reboot"/>
<deny user="john"/>
<deny group="enemies"/>
The <deny> element's attributes determine whether the deny
"matches" a particular action. If it matches, the action is denied
(unless later rules in the config file allow it).
send_destination and receive_sender rules mean that messages may not be sent to
or received from the *owner* of the given name, not that they may not be sent
*to that name*. That is, if a connection owns services A, B, C, and sending to
A is denied, sending to B or C will not work either.
The other send_* and receive_* attributes are purely
textual/
by-value matches
against the given field in the message header.
"Eavesdropping" occurs when an application receives a message that
was explicitly addressed to a name the application does not own, or is a reply
to such a message. Eavesdropping thus only applies to messages that are
addressed to services and replies to such messages (
i.e. it does not apply to
For <allow>, eavesdrop="true" indicates that the rule matches
even when eavesdropping. eavesdrop="false" is the default and means
that the rule only allows messages to go to their specified recipient. For
<deny>, eavesdrop="true" indicates that the rule matches only
eavesdropping. eavesdrop="false" is the default for <deny>
also, but here it means that the rule applies always, even when not
eavesdropping. The eavesdrop attribute can only be combined with send and
receive rules (with send_* and receive_* attributes).
The [send|receive]_requested_reply attribute works similarly to the eavesdrop
attribute. It controls whether the <deny> or <allow> matches a
reply that is expected (corresponds to a previous method call message). This
attribute only makes sense for reply messages (errors and method returns), and
is ignored for other message types.
For <allow>, [send|receive]_requested_reply="true" is the
default and indicates that only requested replies are allowed by the rule.
[send|receive]_requested_reply="false" means that the rule allows any
reply even if unexpected.
For <deny>, [send|receive]_requested_reply="false" is the
default but indicates that the rule matches only when the reply was not
requested. [send|receive]_requested_reply="true" indicates that the
rule applies always, regardless of pending reply state.
user and group denials mean that the given user or group may not connect to the
For "name", "username", "groupname", etc. the
character "*" can be substituted, meaning "any". Complex
globs like "
foo.bar.*" are not allowed for now because they would be
work to implement and maybe encourage sloppy security anyway.
It does not make sense to deny a user or group inside a <policy> for
a user or group;
user/
group denials can only be inside
context="default" or context="mandatory" policies.
A single <deny> rule may specify combinations of attributes such as
send_destination and send_interface and send_type. In this case, the denial
applies only if both attributes match the message being denied.
e.g. <deny
send_interface="
foo.bar" send_destination="
foo.blah"/>
would deny messages with the given interface AND the given bus name. To get an
OR effect you specify multiple <deny> rules.
You can not include both send_ and receive_ attributes on the same rule, since
"whether the message can be sent" and "whether it can be
received" are evaluated separately.
in messages is optional. In particular, do NOT specify <deny
send_interface="
org.
foo.
Bar"/>! This will cause no-interface
messages to be blocked for all services, which is almost certainly not what you
intended. Always use rules of the form:
The <selinux> element contains settings related to Security Enhanced
Linux. More details below. Note, SELinux is not supported on Solaris.
An <associate> element appears below an <selinux> element and
creates a mapping. Right now only one kind of association is possible:
This means that if a connection asks to own the name
of the connection and the target context will be "foo_t" - see the
short discussion of SELinux below.
Note, the context here is the target context when requesting a name, NOT the
context of the connection owning the name.
There is currently no way to set a default for owning any name, if we add this
syntax it will look like:
<associate own="*" context="foo_t"/>
If you find a reason this is useful, let the developers know. Right now the
default will be the security context of the bus itself.
If two <associate> elements specify the same name, the element appearing
later in the configuration file will be used.
SELinux is not supported on Solaris.
<
variablelist termlength="xtranarrow">
Every subject (process) and object (
e.g. file, socket, IPC object, etc) in the
system is assigned a collection of security attributes, known as a security
context. A security context contains all of the security attributes associated
with a particular subject or object that are relevant to the security policy.
</
listitem></
varlistentry>
In order to better encapsulate security contexts and to provide greater
efficiency, the policy enforcement code of SELinux typically handles security
identifiers (SIDs) rather than security contexts. A SID is an integer that is
mapped by the security server to a security context at runtime.
</
listitem></
varlistentry>
When a security decision is required, the policy enforcement code passes a pair
of SIDs (typically the SID of a subject and the SID of an object, but sometimes
a pair of subject SIDs or a pair of object SIDs), and an object security class
to the security server. The object security class indicates the kind of object,
e.g. a process, a regular file, a directory, a TCP socket, etc.
</
listitem></
varlistentry>
Access decisions specify whether or not a permission is granted for a given
pair of SIDs and class. Each object class has a set of associated permissions
defined to control operations on objects with that class.
</
listitem></
varlistentry>
D\-Bus performs SELinux security checks in two places.
First, any time a message is routed from one connection to another connection,
the bus daemon will check permissions with the security context of the first
connection as source, security context of the second connection as target,
object class "dbus" and requested permission "send_msg".
If a security context is not available for a connection (impossible when using
UNIX domain sockets), then the target context used is the context of the bus
daemon itself. There is currently no way to change this default, because we
are assuming that only UNIX domain sockets will be used to connect to the
systemwide bus. If this changes, we will probably add a way to set the default
Second, any time a connection asks to own a name, the bus daemon will check
permissions with the security context of the connection as source, the security
context specified for the name in the config file as target, object class
"dbus" and requested permission "acquire_svc".
The security context for a bus name is specified with the <associate>
element described earlier in this document. If a name has no security context
associated in the configuration file, the security context of the bus daemon
If you are trying to figure out where your messages are going or why you are
not getting messages, there are several things you can try.
Remember that the system bus is heavily locked down and if you have not
installed a security policy file to allow your message through, it will not
work. For the session bus, this is not a concern.
The simplest way to figure out what is happening on the bus is to run the
<
citerefentry><
refentrytitle>dbus-monitor</
refentrytitle>
<
manvolnum>1</
manvolnum></
citerefentry>
program, which comes with the D\-Bus package.
You can also send test messages with
<
citerefentry><
refentrytitle>dbus-send</
refentrytitle>
<
manvolnum>1</
manvolnum></
citerefentry>.
These programs have their own man pages.
If you want to know what the daemon itself is doing, you might consider running
a separate copy of the daemon to test against. This will allow you to put the
daemon under a debugger, or run it with verbose output, without messing up your
real session and system daemons.
To run a separate test copy of the daemon, for example, you might open a
DBUS_VERBOSE=1 &cmd; --session --print-address
The test daemon address will be printed when the daemon starts. You will need
to copy-and-paste this address and use it as the value of the
DBUS_SESSION_BUS_ADDRESS environment variable when you launch the applications
you want to test. This will cause those applications to connect to your test
bus instead of the DBUS_SESSION_BUS_ADDRESS of your real session bus.
DBUS_VERBOSE=1 will have NO EFFECT unless your copy of D\-Bus was compiled with
verbose mode enabled. This is not recommended in production builds due to
performance impact. You may need to rebuild D\-Bus if your copy was not built
with debugging in mind. (DBUS_VERBOSE also affects the D\-Bus library and thus
applications using D\-Bus; it may be useful to see verbose output on both the
client side and from the daemon.)
If you want to get fancy, you can create a custom bus configuration for your
<
filename>
system.conf</
filename> files that define the two default
configurations for example). This would allow you to specify a different
directory for <
filename>.service</
filename> files, for example.
<
refsect1 id="dbus-daemon-1-exam"><
title>&exam-tt;</
title>
<
para><
screen>example% <
userinput>&cmd; </
userinput></
screen></
para>
<
refsect1 id="dbus-daemon-1-file"><
title>&file-tt;</
title>
The following files are used by this application:
<
variablelist termlength="wholeline">
<
term><
filename>/
usr/
lib/&cmd;</
filename></
term>
Executable for <
command>&cmd;</
command>
</
listitem></
varlistentry>
Directory containing standard D\-Bus session services.
</
listitem></
varlistentry>
Directory containing standard D\-Bus systemwide services.
</
listitem></
varlistentry>
Configuration file for D\-Bus session services.
</
listitem></
varlistentry>
Configuration file for D\-Bus system services.
</
listitem></
varlistentry>
</
variablelist></
refsect1>
<
refsect1 id="dbus-daemon-1-attr"><
title>&attr-tt;</
title>
See <
olink targetdocent="REFMAN5" localinfo="attributes-5">
<
citerefentry><
refentrytitle>attributes</
refentrytitle>
<
manvolnum>5</
manvolnum></
citerefentry></
olink>
for descriptions of the following attributes:
<
informaltable frame="all">
<
tgroup cols="2" colsep="1" rowsep="1">
<
colspec colname="COLSPEC0" colwidth="1*">
<
colspec colname="COLSPEC1" colwidth="1*">
<
entry align="center" valign="middle">ATTRIBUTE TYPE</
entry>
<
entry align="center" valign="middle">ATTRIBUTE VALUE</
entry>
<
entry><
para>Availability</
para></
entry>
<
entry><
para>SUNWdbus</
para></
entry>
<
entry colname="COLSPEC0"><
para>Interface stability</
para></
entry>
<
entry colname="COLSPEC1"><
para>Volatile</
para></
entry>
<
refsect1 id="dbus-daemon-1-also"><
title>&also-tt;</
title>
<!--Reference to another man page--> <!--Reference to a Help manual--> <!--Reference to a book.--> More information can be found at:
<
citerefentry><
refentrytitle>dbus-binding-tool</
refentrytitle><
manvolnum>1</
manvolnum></
citerefentry>,
<
citerefentry><
refentrytitle>dbus-cleanup-sockets</
refentrytitle><
manvolnum>1</
manvolnum></
citerefentry>,
<
citerefentry><
refentrytitle>dbus-launch</
refentrytitle><
manvolnum>1</
manvolnum></
citerefentry>,
<
citerefentry><
refentrytitle>dbus-monitor</
refentrytitle><
manvolnum>1</
manvolnum></
citerefentry>,
<
citerefentry><
refentrytitle>dbus-send</
refentrytitle><
manvolnum>1</
manvolnum></
citerefentry>,
<
citerefentry><
refentrytitle>dbus-uuidgen</
refentrytitle><
manvolnum>1</
manvolnum></
citerefentry>,
<
citerefentry><
refentrytitle>svcadm</
refentrytitle><
manvolnum>1m</
manvolnum></
citerefentry>,
<
citerefentry><
refentrytitle>libdbus-glib-1</
refentrytitle><
manvolnum>3</
manvolnum></
citerefentry>,
<
citerefentry><
refentrytitle>attributes</
refentrytitle><
manvolnum>5</
manvolnum></
citerefentry>,
<
citerefentry><
refentrytitle>environ</
refentrytitle><
manvolnum>5</
manvolnum></
citerefentry>,
<
citerefentry><
refentrytitle>smf</
refentrytitle><
manvolnum>5</
manvolnum></
citerefentry>
<
refsect1 id="dbus-daemon-1-note"><
title>¬e-tt;</
title>
For authorship information refer to
Updated by Brian Cameron, Sun Microsystems Inc., 2007.
Please send bug reports to the D\-Bus mailing list or bug