update document about listenable address in dbus spec and dbus-damon manpage
@chengwei
Submitted by Chengwei Yang Assigned to D-Bus Maintainers
Description
Copied from http://lists.freedesktop.org/archives/dbus/2013-July/015718.html
Hi List,
I just found that there is an inconsistent issue of message bus server address.
There are two ways to specify the message bus server addresses, from
command line option "--address" or configure "<listen>
" element in bus
config file.
However, they behave a little different as below.
Quote from DBus Spec
[FIXME clarify if attempting to connect to each is a requirement or just a suggestion] When connecting to a server, multiple server addresses can be separated by a semi-colon. The library will then try to connect to the first address and if that fails, it'll try to connect to the next one specified, and so forth. For example
unix:path=/tmp/dbus-test;unix:path=/tmp/dbus-test2
Quote from dbus-daemon(1)
· <listen>
Add an address that the bus should listen on. The address
is in the standard D-Bus format that contains a transport
name plus possible parameters/options.
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, apps will try to connect to the last `<listen>`
address first.
So seems that we're saying: there is no way to listen on multiple
address if you're using '--address' option, if that is your case,
configure '<listen>
' in config file instead.
Should this to be fixed?
If so, how? Align '<listen>
(man page)' with '--address(dbus spec)' or
the reverse?
-- Thanks, Chengwei
Version: 1.5