Log Message:
-----------
 - Add links into the table documentation...

 - Adding in info on path handling...

Modified Files:
--------------
    slony1-engine/doc/adminguide:
        adminscripts.sgml (r1.16 -> r1.17)
        monitoring.sgml (r1.12 -> r1.13)
        prerequisites.sgml (r1.11 -> r1.12)
        reshape.sgml (r1.11 -> r1.12)

-------------- next part --------------
Index: monitoring.sgml
===================================================================
RCS file: /usr/local/cvsroot/slony1/slony1-engine/doc/adminguide/monitoring.sgml,v
retrieving revision 1.12
retrieving revision 1.13
diff -Ldoc/adminguide/monitoring.sgml -Ldoc/adminguide/monitoring.sgml -u -w -r1.12 -r1.13
--- doc/adminguide/monitoring.sgml
+++ doc/adminguide/monitoring.sgml
@@ -81,19 +81,24 @@
 including such things as:
 
 <itemizedlist>
-<listitem><para> Checking <envar> sl_listen </envar> for some
+<listitem><para> Checking  <link
+linkend="table.sl-listen"> <envar>sl_listen</envar></link> for some
 <quote>analytically determinable</quote> problems.  It lists paths
 that are not covered.</para></listitem>  
 
 <listitem><para> Providing a summary of events by origin node</para>
 
-<para> If a node hasn't submitted any events in a while, that likely suggests a problem.</para></listitem>
+<para> If a node hasn't submitted any events in a while, that likely
+suggests a problem.</para></listitem>
 
-<listitem><para> Summarizes the <quote>aging</quote> of table <envar>sl_confirm</envar></para>
+<listitem><para> Summarizes the <quote>aging</quote> of table <link
+linkend="table.sl-confirm"> <envar>sl_confirm</envar></link> </para>
 
 <para> If one or another of the nodes in the cluster hasn't reported
-back recently, that tends to lead to cleanups of tables like <envar>
-sl_log_1 </envar> and <envar> sl_seqlog </envar> not taking place.</para></listitem>
+back recently, that tends to lead to cleanups of tables like <link
+linkend="table.sl-log-1"> <envar>sl_log_1</envar></link> and <link
+linkend="table.sl-seqlog"> <envar>sl_seqlog</envar></link> not taking
+place.</para></listitem>
 
 <listitem><para> Summarizes what transactions have been running for a
 long time</para>
Index: adminscripts.sgml
===================================================================
RCS file: /usr/local/cvsroot/slony1/slony1-engine/doc/adminguide/adminscripts.sgml,v
retrieving revision 1.16
retrieving revision 1.17
diff -Ldoc/adminguide/adminscripts.sgml -Ldoc/adminguide/adminscripts.sgml -u -w -r1.16 -r1.17
--- doc/adminguide/adminscripts.sgml
+++ doc/adminguide/adminscripts.sgml
@@ -222,8 +222,11 @@
 <sect2 id="regenlisten"><title>regenerate-listens.pl</title>
 
 <para>This script connects to a &slony1; node, and queries various
-tables (sl_set, sl_node, sl_subscribe, sl_path) to compute what
-<command><link linkend="stmtstorelisten"> STORE
+tables (<link linkend="table.sl-set"> <envar>sl_set</envar></link>,
+<link linkend="table.sl-node"> <envar>sl_node</envar></link>, <link
+linkend="table.sl-subscribe"> <envar>sl_subscribe</envar></link>,
+<link linkend="table.sl-path"> <envar>sl_path</envar></link>) to
+compute what <command><link linkend="stmtstorelisten"> STORE
 LISTEN</link></command> requests should be submitted to the
 cluster.</para>
 
Index: prerequisites.sgml
===================================================================
RCS file: /usr/local/cvsroot/slony1/slony1-engine/doc/adminguide/prerequisites.sgml,v
retrieving revision 1.11
retrieving revision 1.12
diff -Ldoc/adminguide/prerequisites.sgml -Ldoc/adminguide/prerequisites.sgml -u -w -r1.11 -r1.12
--- doc/adminguide/prerequisites.sgml
+++ doc/adminguide/prerequisites.sgml
@@ -165,10 +165,10 @@
 
 <para>A possible workaround for this, in environments where firewall
 rules are particularly difficult to implement, may be to establish
-<ulink url="http://www.brandonhutchinson.com/ssh_tunnelling.html"> SSH
-Tunnels </ulink> that are created on each host that allow remote
-access through a local IP address such as 127.0.0.1, using a different
-port for each destination.</para>
+<ulink url="http://www.brandonhutchinson.com/ssh_tunnelling.html"
+id="tunnelling"> SSH Tunnels </ulink> that are created on each host
+that allow remote access through a local IP address such as 127.0.0.1,
+using a different port for each destination.</para>
 
 <para> Note that <application>slonik</application> and the
 <application>slon</application> instances need no special connections
Index: reshape.sgml
===================================================================
RCS file: /usr/local/cvsroot/slony1/slony1-engine/doc/adminguide/reshape.sgml,v
retrieving revision 1.11
retrieving revision 1.12
diff -Ldoc/adminguide/reshape.sgml -Ldoc/adminguide/reshape.sgml -u -w -r1.11 -r1.12
--- doc/adminguide/reshape.sgml
+++ doc/adminguide/reshape.sgml
@@ -31,10 +31,13 @@
 SUBSCRIBE SET</link> </command> might change the paths as a
 side-effect.  See <link linkend="listenpaths"> Slony Listen Paths
 </link> for more information about this.  In version 1.1 and later, it
-is likely that the generation of <envar>sl_listen</envar> entries will
-be entirely automated, where they will be regenerated when changes are
-made to sl_path or sl_subscribe, thereby making it unnecessary to even
-think about <command> <link linkend="stmtstorelisten"> STORE LISTEN
+is likely that the generation of <link linkend="table.sl-listen">
+<envar>sl_listen</envar></link> entries will be entirely automated,
+where they will be regenerated when changes are made to <link
+linkend="table.sl-path"> <envar>sl_path</envar></link> or <link
+linkend="table.sl-path"> <envar>sl_subscribe</envar></link>, thereby
+making it unnecessary to even think about <command> <link
+linkend="stmtstorelisten"> STORE LISTEN
 </link></command>.</para></listitem>
 
 </itemizedlist>