Log Message:
-----------
Fix up tagging of documents; did a lot of SGML normalization.

Modified Files:
--------------
    slony1-engine/doc/adminguide:
        addthings.sgml (r1.9 -> r1.10)
        adminscripts.sgml (r1.14 -> r1.15)
        cluster.sgml (r1.8 -> r1.9)
        concepts.sgml (r1.9 -> r1.10)
        ddlchanges.sgml (r1.10 -> r1.11)
        defineset.sgml (r1.10 -> r1.11)
        dropthings.sgml (r1.10 -> r1.11)
        failover.sgml (r1.10 -> r1.11)
        faq.sgml (r1.16 -> r1.17)
        firstdb.sgml (r1.9 -> r1.10)
        help.sgml (r1.10 -> r1.11)
        installation.sgml (r1.9 -> r1.10)
        intro.sgml (r1.9 -> r1.10)
        legal.sgml (r1.5 -> r1.6)
        listenpaths.sgml (r1.11 -> r1.12)
        maintenance.sgml (r1.10 -> r1.11)
        monitoring.sgml (r1.11 -> r1.12)
        plainpaths.sgml (r1.1 -> r1.2)
        reshape.sgml (r1.10 -> r1.11)
        slon.sgml (r1.9 -> r1.10)
        slonik.sgml (r1.10 -> r1.11)
        slony.sgml (r1.13 -> r1.14)
        startslons.sgml (r1.8 -> r1.9)
        subscribenodes.sgml (r1.9 -> r1.10)
        usingslonik.sgml (r1.3 -> r1.4)
        versionupgrade.sgml (r1.2 -> r1.3)

-------------- next part --------------
Index: usingslonik.sgml
===================================================================
RCS file: /usr/local/cvsroot/slony1/slony1-engine/doc/adminguide/usingslonik.sgml,v
retrieving revision 1.3
retrieving revision 1.4
diff -Ldoc/adminguide/usingslonik.sgml -Ldoc/adminguide/usingslonik.sgml -u -w -r1.3 -r1.4
--- doc/adminguide/usingslonik.sgml
+++ doc/adminguide/usingslonik.sgml
@@ -358,10 +358,32 @@
 
 <para> There are cases where it may make sense to directly use the
 stored functions that implement the various pieces of &slony1;.
-Slonik doesn't do terribly much <quote/magic;/ it is common for Slonik
-commands to simply involve deciding on a node at which to apply a
-command, and then submit a SQL query consisting of a call to one of
+Slonik doesn't do terribly much <quote>magic;</quote> it is common for
+Slonik commands to simply involve deciding on a node at which to apply
+a command, and then submit a SQL query consisting of a call to one of
 the &slony1; stored functions.</para>
+
+<para> The developers of &slony1; anticipate that interested parties
+may wish to develop graphical tools as an alternative to Slonik; it
+would be entirely appropriate in such cases to submit configuration
+requests directly via the stored functions.
+
+<para> When debugging problems in <quote>troubled</quote> &slony1;
+clusters, it has also occasionally proven useful to use the stored
+functions.  This has been particularly useful for cases where
+<envar>sl_listen</envar> configuration has been broken, and events
+have not been propagating properly.  The <quote>easiest</quote> fix
+was to:</para>
+
+<para> <command> select
+_slonycluster.droplisten(li_origin,li_provider,li_receiver) from
+_slonycluster.sl_listen;</command></para>
+
+<para> <command> select _slonycluster.storelisten(pa_server,
+pa_server, pa_client) from _slonycluster.sl_path;</command></para>
+
+<para> 
+
 </sect1>
 <!-- Keep this comment at the end of the file
 Local variables:
Index: plainpaths.sgml
===================================================================
RCS file: /usr/local/cvsroot/slony1/slony1-engine/doc/adminguide/plainpaths.sgml,v
retrieving revision 1.1
retrieving revision 1.2
diff -Ldoc/adminguide/plainpaths.sgml -Ldoc/adminguide/plainpaths.sgml -u -w -r1.1 -r1.2
--- doc/adminguide/plainpaths.sgml
+++ doc/adminguide/plainpaths.sgml
@@ -1,18 +1,18 @@
 <!-- $Id$ -->
 <sect1 id="plainpaths"><title><productname>Slony-I</productname> Path Communications</title>
 
-<para>To Do...
+<para> <productname>Slony-I</productname></para>
 
 <para> Basically need to discuss what STORE PATHs are about, and
 distinguish them from the admin conninfo entries in the slonik
-preamble.
+preamble.</para>
 
 <para> This isn't an issue for people with simple networks; it matters
 for those with complex firewall configurations, nodes at multiple
 locations, and the issue where nodes may not be able to all talk to
-one another at a uniform set of network addresses.
+one another at a uniform set of network addresses.</para>
 
-<para> There is also room for discussion of SSH tunnelling here...
+<para> There is also room for discussion of SSH tunnelling here...</para>
 
 </sect1>
 <!-- Keep this comment at the end of the file
@@ -24,8 +24,7 @@
 sgml-always-quote-attributes:t
 sgml-indent-step:1
 sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"./reference.ced"
+sgml-parent-document:"book.sgml"
 sgml-exposed-tags:nil
 sgml-local-catalogs:("/usr/lib/sgml/catalog")
 sgml-local-ecat-files:nil
Index: slony.sgml
===================================================================
RCS file: /usr/local/cvsroot/slony1/slony1-engine/doc/adminguide/slony.sgml,v
retrieving revision 1.13
retrieving revision 1.14
diff -Ldoc/adminguide/slony.sgml -Ldoc/adminguide/slony.sgml -u -w -r1.13 -r1.14
--- doc/adminguide/slony.sgml
+++ doc/adminguide/slony.sgml
@@ -13,7 +13,7 @@
 <book id="slony">
   <title>&slony1; &version; Documentation</title>
   <bookinfo>
-    <corpauthor>The &postgres; Global Development Group</corpauthor>
+    <corpauthor>The PostgreSQL Global Development Group</corpauthor>
     <author>
       <firstname>Christopher</firstname>
       <surname>Browne</surname>
@@ -75,13 +75,12 @@
 
  &faq;
  &schemadoc;
-</part>
 
-<part id="commandreferencec">
+<part id="commandreference">
     <title>Core &slony1; Programs</title>
 	&slon;
 	&slonik;
-        &usingslonik;
+        &slonikref;
 </part>
 
 &bookindex;