From f3fd4d60ad5de9f0c6576f6e100f944792fed255 Mon Sep 17 00:00:00 2001 From: Ralf Habacker Date: Sat, 10 Mar 2007 08:04:39 +0000 Subject: * dbus/dbus-sysdeps.h (_dbus_listen_tcp_socket): changed type or port to pointer, because the port is given back. * dbus/dbus-server-socket.c (_dbus_server_new_for_tcp_socket): implemented returning tcp port. Skipping port parameter and non integer port values in config statement needs more effort. * dbus/dbus-sysdeps-unix.c, dbus/dbus-sysdeps-win.c (_dbus_listen_tcp_socket): return the real used tcp port. * bus/dbus-daemon.1.in: added tcp examples --- bus/dbus-daemon.1.in | 11 +++++++++++ 1 file changed, 11 insertions(+) (limited to 'bus') diff --git a/bus/dbus-daemon.1.in b/bus/dbus-daemon.1.in index 5c846836..acee933a 100644 --- a/bus/dbus-daemon.1.in +++ b/bus/dbus-daemon.1.in @@ -210,6 +210,9 @@ a transport name plus possible parameters/options. .PP Example: unix:path=/tmp/foo +.PP +Example: tcp:host=localhost,port=1234 + .PP If there are multiple elements, then the bus listens on multiple addresses. The bus will pass its address to @@ -217,6 +220,14 @@ started services or other interested parties with the last address given in first. That is, apps will try to connect to the last address first. +.PP +A special case is using a port number of zero which means to +pick up a random free port. The real used port number could be retrieved +by using the --print-address command line parameter. + +.PP +Example: tcp:host=localhost,port=0 + .TP .I "" -- cgit