Log Message:
-----------
start slons docs - note the 1.2 changes

Modified Files:
--------------
    slony1-engine/doc/adminguide:
        startslons.sgml (r1.16 -> r1.17)

-------------- next part --------------
Index: startslons.sgml
===================================================================
RCS file: /usr/local/cvsroot/slony1/slony1-engine/doc/adminguide/startslons.sgml,v
retrieving revision 1.16
retrieving revision 1.17
diff -Ldoc/adminguide/startslons.sgml -Ldoc/adminguide/startslons.sgml -u -w -r1.16 -r1.17
--- doc/adminguide/startslons.sgml
+++ doc/adminguide/startslons.sgml
@@ -45,7 +45,24 @@
 </itemizedlist>
 </para>
 
-<para>There are two <quote>watchdog</quote> scripts currently available:
+<warning><para> Do <emphasis>not</emphasis> run a slon that is
+responsible to service a particular node across a WAN link if at all
+possible.  Any problems with that connection can kill the connection
+whilst leaving <quote>zombied</quote> database connections on the node
+that (typically) will not die off for around two hours.  This prevents
+starting up another slon, as described <xref
+linkend="multipleslonconnections">. </para> </warning>
+
+
+<para> Historically, <application>slon</application> processes have
+been fairly fragile, dying if they encounter just about any
+significant error.  This behaviour mandated running some form of
+<quote>watchdog</quote> which would watch to make sure that if one
+<application>slon</application> fell over, it would be replaced by
+another. </para>
+
+<para>There are two <quote>watchdog</quote> scripts currently
+available in the &slony1; source tree:
 
 <itemizedlist>
 
@@ -76,19 +93,21 @@
 event.  More recently, the script has been changed to detect
 <command>COPY SET</command> in progress.</para>
 
+<para>In &slony1; version 1.2, the structure of the
+<application>slon</application> has been revised fairly substantially
+to make it much less fragile.  The main process should only die off if
+you expressly signal it asking it to be killed. </para>
+
+<para> A new approach is available in the <xref
+linkend="launchclusters"> script which uses
+<application>slon</application> configuration files and which may be
+invoked as part of your system startup process.</para>
+
 </sect1>
-<!-- Keep this comment at the end of the file
-Local variables:
-mode:sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:"book.sgml"
+<!-- Keep this comment at the end of the file Local variables:
+mode:sgml sgml-omittag:nil sgml-shorttag:t
+sgml-minimize-attributes:nil sgml-always-quote-attributes:t
+sgml-indent-step:1 sgml-indent-data:t sgml-parent-document:"book.sgml"
 sgml-exposed-tags:nil
 sgml-local-catalogs:("/usr/lib/sgml/catalog")
-sgml-local-ecat-files:nil
-End:
--->
+sgml-local-ecat-files:nil End: -->