Update of /home/cvsd/slony1/slony1-engine/doc/adminguide
In directory main.slony.info:/tmp/cvs-serv26733

Modified Files:
	failover.sgml 
Log Message:
Fix sgml errors


Index: failover.sgml
===================================================================
RCS file: /home/cvsd/slony1/slony1-engine/doc/adminguide/failover.sgml,v
retrieving revision 1.27
retrieving revision 1.28
diff -C2 -d -r1.27 -r1.28
*** failover.sgml	24 Mar 2008 15:57:34 -0000	1.27
--- failover.sgml	13 Oct 2008 19:29:12 -0000	1.28
***************
*** 41,45 ****
  on node1.  Both databases are up and running and replication is more
  or less in sync.  We do controlled switchover using <xref
! linkend="stmtmoveset">.
  
  <itemizedlist>
--- 41,45 ----
  on node1.  Both databases are up and running and replication is more
  or less in sync.  We do controlled switchover using <xref
! linkend="stmtmoveset">.</para>
  
  <itemizedlist>
***************
*** 58,62 ****
  the database that has been promoted to the <quote/master/ role.  There
  are a number of ways that this may be configured, and therefore, a
! number of possible methods for accomplishing the change:
  
  <itemizedlist>
--- 58,62 ----
  the database that has been promoted to the <quote/master/ role.  There
  are a number of ways that this may be configured, and therefore, a
! number of possible methods for accomplishing the change:</para>
  
  <itemizedlist>
***************
*** 120,124 ****
  seconds.</para></listitem>
  
! </itemizedlist></para>
  
  <para> You may now simply shutdown the server hosting node1 and do
--- 120,124 ----
  seconds.</para></listitem>
  
! </itemizedlist>
  
  <para> You may now simply shutdown the server hosting node1 and do
***************
*** 267,271 ****
  to forcibly knock the failed node off the network in order to prevent
  applications from getting confused.  This could take place via having
! an SNMP interface that does some combination of the following:
  
  <itemizedlist>
--- 267,271 ----
  to forcibly knock the failed node off the network in order to prevent
  applications from getting confused.  This could take place via having
! an SNMP interface that does some combination of the following:</para>
  
  <itemizedlist>
***************
*** 288,292 ****
  
  </itemizedlist>
- </para>
  </sect2>
  
--- 288,291 ----