[Inteproxy-commits] r107 - trunk

[scm-commit@wald.intevation.org]

Author: bh
Date: 2007-10-23 20:50:26 +0200 (Tue, 23 Oct 2007)
New Revision: 107

Modified:
   trunk/ChangeLog
   trunk/demo.cfg
Log:
* demo.cfg: Explain how to deal with multiple server on the same
remote host to avoid problems that can occur with multiple
sections with the same name


Modified: trunk/ChangeLog
===================================================================
--- trunk/ChangeLog	2007-08-31 14:51:18 UTC (rev 106)
+++ trunk/ChangeLog	2007-10-23 18:50:26 UTC (rev 107)
@@ -1,3 +1,9 @@
+2007-10-23  Bernhard Herzog  <bh at intevation.de>
+
+	* demo.cfg: Explain how to deal with multiple server on the same
+	remote host to avoid problems that can occur with multiple
+	sections with the same name
+
 2007-08-31  Jan-Oliver Wagner  <jan-oliver.wagner at intevation.de>
 
 	* HowTo-Release.txt: Optimized tar-archive creation.

Modified: trunk/demo.cfg
===================================================================
--- trunk/demo.cfg	2007-08-31 14:51:18 UTC (rev 106)
+++ trunk/demo.cfg	2007-10-23 18:50:26 UTC (rev 107)
@@ -3,7 +3,9 @@
 # This file defines how different remote servers are to be accessed.
 # There is one section for each remote server.  How the sections are
 # named doesn't really matter but it's a good idea to include the full
-# domain name in the section name.  
+# domain name in the section name.  If you want to access to different
+# servers on the same host, be careful to give both sections different
+# names, by e.g. appending some more information about the server.
 #
 # There might be some additional section with predefined names in the
 # future for other inteproxy settings.  The names for those section will