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

Modified Files:
	firstdb.sgml 
Log Message:
Fixes to altperl example, per bug #48

Also a rewording of material about altperl


Index: firstdb.sgml
===================================================================
RCS file: /home/cvsd/slony1/slony1-engine/doc/adminguide/firstdb.sgml,v
retrieving revision 1.26
retrieving revision 1.27
diff -C2 -d -r1.26 -r1.27
*** firstdb.sgml	24 Mar 2008 15:57:34 -0000	1.26
--- firstdb.sgml	18 Apr 2008 16:14:42 -0000	1.27
***************
*** 160,196 ****
  procedures in the master/slave (node) databases. </para>
  
- <sect3><title>Using the altperl scripts</title>
- 
- <indexterm><primary> altperl script usage </primary></indexterm>
- 
- <para>
- Using the <xref linkend="altperl"> scripts is an easy way to get started.  The
- <command>slonik_build_env</command> script will generate output providing
- details you need to  omplete building a <filename>slon_tools.conf</filename>. 
- An example <filename>slon_tools.conf</filename> is provided in the distribution
- to get you started.  The altperl scripts will all reference
- this central configuration file in the future to ease administration. Once 
- slon_tools.conf has been created, you can proceed as follows:
- </para>
- 
- <programlisting>
- # Initialize cluster:
- $ slonik_init_cluster  | slonik 
- 
- # Start slon  (here 1 and 2 are node numbers)
- $ slon_start 1    
- $ slon_start 2
- 
- # Create Sets (here 1 is a set number)
- $ slonik_create_set 1             
- 
- # subscribe set to second node (1= set ID, 2= node ID)
- $ slonik_subscribe_set  2 | slonik
- </programlisting>
- 
- <para> You have now replicated your first database.  You can skip the following section
- of documentation if you'd like, which documents more of a <quote>bare-metal</quote> approach.</para>
- </sect3>
- 
  <sect3><title>Using slonik command directly</title>
  
--- 160,163 ----
***************
*** 391,394 ****
--- 358,400 ----
  diagnostic information including the logs generated by &lslon;
  processes and the output of &lteststate;. </para></sect3>
+ 
+ <sect3><title>Using the altperl scripts</title>
+ 
+ <indexterm><primary> altperl script example </primary></indexterm>
+ 
+ <para>
+ Using the <xref linkend="altperl"> scripts is an alternative way to
+ get started; it allows you to avoid writing slonik scripts, at least
+ for some of the simple ways of configuring &slony1;.  The
+ <command>slonik_build_env</command> script will generate output
+ providing details you need to build a
+ <filename>slon_tools.conf</filename>, which is required by these
+ scripts.  An example <filename>slon_tools.conf</filename> is provided
+ in the distribution to get you started.  The altperl scripts all
+ reference this central configuration file centralize cluster
+ configuration information. Once slon_tools.conf has been created, you
+ can proceed as follows:
+ </para>
+ 
+ <programlisting>
+ # Initialize cluster:
+ $ slonik_init_cluster  | slonik 
+ 
+ # Start slon  (here 1 and 2 are node numbers)
+ $ slon_start 1    
+ $ slon_start 2
+ 
+ # Create Sets (here 1 is a set number)
+ $ slonik_create_set 1 | slonik             
+ 
+ # subscribe set to second node (1= set ID, 2= node ID)
+ $ slonik_subscribe_set  2 | slonik
+ </programlisting>
+ 
+ <para> You have now replicated your first database.  You can skip the
+ following section of documentation if you'd like, which documents more
+ of a <quote>bare-metal</quote> approach.</para>
+ </sect3>
+ 
  </sect2>
  </sect1>