dbus/bus dbus-daemon.1.in,1.6,1.7

[Ralf Habacker]

Update of /cvs/dbus/dbus/bus
In directory kemper:/tmp/cvs-serv18111/bus

Modified Files:
	dbus-daemon.1.in 
Log Message:
* 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 <listen> 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 <listen> tcp examples

Index: dbus-daemon.1.in
===================================================================
RCS file: /cvs/dbus/dbus/bus/dbus-daemon.1.in,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -d -r1.6 -r1.7
--- dbus-daemon.1.in	1 Feb 2007 22:41:23 -0000	1.6
+++ dbus-daemon.1.in	10 Mar 2007 08:04:39 -0000	1.7
@@ -211,12 +211,23 @@
 Example: <listen>unix:path=/tmp/foo</listen>
 
 .PP
+Example: <listen>tcp:host=localhost,port=1234</listen>
+
+.PP
 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.
 
+.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: <listen>tcp:host=localhost,port=0</listen>
+
 .TP
 .I "<auth>"