add a note about the new DBUS reconnection behaviour of avahi-daemon

git-svn-id: file:///home/lennart/svn/public/avahi/trunk@1198 941a03a8-eaeb-0310-b9a0-b1bbd8fe43fe

diff --git a/man/avahi-daemon.conf.5.xml.in b/man/avahi-daemon.conf.5.xml.in
index 5f59f16d1f8fa3bdf06f57c12cf265c9a1885aa7..7dff0974c1d957f919fd2045190a7b4ddc25fa75 100644 (file)
--- a/man/avahi-daemon.conf.5.xml.in
+++ b/man/avahi-daemon.conf.5.xml.in
@@ -98,10 +98,12 @@
         <p><opt>enable-dbus=</opt> Takes either "yes", "no" or
         "warn". If set to "yes" avahi-daemon connects to D-BUS,
         offering an object oriented client API. It is only available
-        if avahi has been compiled with <opt>--enable-dbus</opt> in
+        if Avahi has been compiled with <opt>--enable-dbus</opt> in
         which case it defaults to "yes". "warn" behaves like "yes",
         but the daemon starts up even when it fails to connect to a
-        D-BUS daemon.</p>
+        D-BUS daemon. In addition, if the connection to the D-BUS
+        daemon is terminated we try to reconnect. (Unless we are in a
+        chroot() environment where this definitely will fail.) </p>
       </option>
 
       <option>