Log Message:
-----------
Fix up tagging problems to admin guide...

Modified Files:
--------------
    slony1-engine/doc/adminguide:
        monitoring.sgml (r1.26 -> r1.27)
        slony.sgml (r1.31 -> r1.32)

-------------- next part --------------
Index: monitoring.sgml
===================================================================
RCS file: /usr/local/cvsroot/slony1/slony1-engine/doc/adminguide/monitoring.sgml,v
retrieving revision 1.26
retrieving revision 1.27
diff -Ldoc/adminguide/monitoring.sgml -Ldoc/adminguide/monitoring.sgml -u -w -r1.26 -r1.27
--- doc/adminguide/monitoring.sgml
+++ doc/adminguide/monitoring.sgml
@@ -734,11 +734,11 @@
 <para> Hmm.  The table isn't in altered replicated state.  That shouldn't be, if replication had been working properly...</para> </listitem>
 
 <listitem><para><command>ERROR: Slony-I: subscribeSet() must be called on provider</command></para> 
-<para> This function should only get called on the provider node.  &slonik; normally handles this right, unless one had wrong DSNs in a &slonik; script...</para>
+<para> This function should only get called on the provider node.  &lslonik; normally handles this right, unless one had wrong DSNs in a &lslonik; script...</para>
 </listitem>
 
 <listitem><para><command>ERROR: Slony-I: subscribeSet(): set % not found</command></para> 
-<para> Hmm.  The provider node isn't aware of this set.  Wrong parms to a &slonik; script?</para> </listitem>
+<para> Hmm.  The provider node isn't aware of this set.  Wrong parms to a &lslonik; script?</para> </listitem>
 
 <listitem><para><command>ERROR: Slony-I: subscribeSet(): set origin and receiver cannot be identical</command></para> 
 <para> Duh, an origin node can't subscribe to itself.</para> </listitem>
@@ -755,7 +755,7 @@
 <listitem><para><command>Slony-I: subscribeSet_int(): set % not found</command></para> 
 <para> This node isn't aware of the set...  Perhaps you submitted wrong parms?</para></listitem>
 <listitem><para><command>Slony-I: unsubscribeSet() must be called on receiver</command></para> 
-<para> Seems obvious...  This probably indicates a bad &slonik; admin DSN...</para></listitem>
+<para> Seems obvious...  This probably indicates a bad &lslonik; admin DSN...</para></listitem>
 <listitem><para><command>Slony-I: Cannot unsubscribe set % while being provider</command></para> 
 
 <para> This should seem obvious; <xref linkend="stmtunsubscribeset"> will fail if a node has dependent subscribers for which it is the provider </para> </listitem>
@@ -790,7 +790,8 @@
 
 <sect2> <title> &nagios; Replication Checks </title>
 
-<indexterm><primary>&nagios; for monitoring replication</primary></indexterm>
+<indexterm><primary>&nagios; for monitoring
+replication</primary></indexterm>
 
 <para> The script in the <filename>tools</filename> directory called
 <command> pgsql_replication_check.pl </command> represents some of the
@@ -947,4 +948,13 @@
 mode:sgml
 sgml-omittag:nil
 sgml-shorttag:t
-sgm
+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:
+-->
Index: slony.sgml
===================================================================
RCS file: /usr/local/cvsroot/slony1/slony1-engine/doc/adminguide/slony.sgml,v
retrieving revision 1.31
retrieving revision 1.32
diff -Ldoc/adminguide/slony.sgml -Ldoc/adminguide/slony.sgml -u -w -r1.31 -r1.32
--- doc/adminguide/slony.sgml
+++ doc/adminguide/slony.sgml
@@ -49,6 +49,7 @@
 <!ENTITY rlistenpaths "<xref linkend=listenpaths>">
 <!ENTITY pglistener "<envar>pg_listener</envar>">
 <!ENTITY lslon "<xref linkend=slon>">
+<!ENTITY lslonik "<xref linkend=slonik>">
 
 ]>