List:Commits« Previous MessageNext Message »
From:paul.dubois Date:February 9 2011 3:33pm
Subject:svn commit - mysqldoc@docsrva: r25021 - in trunk: . refman-5.0 refman-5.1 refman-5.5 refman-5.6 refman-6.0
View as plain text  
Author: paul
Date: 2011-02-09 16:33:36 +0100 (Wed, 09 Feb 2011)
New Revision: 25021

Log:
 r44854@dhcp-213:  paul | 2011-02-09 09:32:58 -0500
 Multiple-server updates


Modified:
   trunk/refman-5.0/dba-multiple-servers.xml
   trunk/refman-5.1/dba-multiple-servers.xml
   trunk/refman-5.5/dba-multiple-servers.xml
   trunk/refman-5.6/dba-multiple-servers.xml
   trunk/refman-6.0/dba-multiple-servers.xml

Property changes on: trunk
___________________________________________________________________
Name: svk:merge
   - 07c7e7b4-24e3-4b51-89d0-6dc09fec6bec:/mysqldoc-local/mysqldoc/trunk:35498
07c7e7b4-24e3-4b51-89d0-6dc09fec6bec:/mysqldoc-local/trunk:46807
4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:43968
4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/trunk:44480
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:66486
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:39036
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/trunk:39546
ebeeeee4-b232-4669-a521-231442eced53:/mysqldoc-local/mysqldoc/trunk:44846
   + 07c7e7b4-24e3-4b51-89d0-6dc09fec6bec:/mysqldoc-local/mysqldoc/trunk:35498
07c7e7b4-24e3-4b51-89d0-6dc09fec6bec:/mysqldoc-local/trunk:46807
4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:43968
4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/trunk:44480
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:66486
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:39036
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/trunk:39546
ebeeeee4-b232-4669-a521-231442eced53:/mysqldoc-local/mysqldoc/trunk:44854


Modified: trunk/refman-5.0/dba-multiple-servers.xml
===================================================================
--- trunk/refman-5.0/dba-multiple-servers.xml	2011-02-09 10:37:50 UTC (rev 25020)
+++ trunk/refman-5.0/dba-multiple-servers.xml	2011-02-09 15:33:36 UTC (rev 25021)
Changed blocks: 5, Lines Added: 78, Lines Deleted: 61; 7273 bytes

@@ -41,7 +41,7 @@
   </para>
 
   <para>
-    It is possible to use a different MySQL server binary per instances,
+    It is possible to use a different MySQL server binary per instance,
     or use the same binary for multiple instances, or any combination of
     the two approaches. For example, you might run a server from MySQL
     &previous-series; and one from MySQL &current-series;, to see how

@@ -57,7 +57,7 @@
     instances. Parameters can be set on the command line, in option
     files, or by setting environment variables. See
     <xref linkend="program-options"/>. To see the values used by a given
-    server, connect to it and execute a <literal role="stmt">SHOW
+    instance, connect to it and execute a <literal role="stmt">SHOW
     VARIABLES</literal> statement.
   </para>
 

@@ -66,7 +66,8 @@
     directory, and each instance should use a different data directory.
     The location is specified using the
     <option role="mysqld">--datadir=<replaceable>path</replaceable></option>
-    option.
+    option. For methods of configuring each instance with its own data
+    directory, see <xref linkend="multiple-data-directories"/>.
   </para>
 
   <warning>

@@ -111,10 +112,10 @@
 
       <para>
         <option role="mysqld">--port</option> controls the port number
-        for TCP/IP connections. (Alternatively, if the host has multiple
+        for TCP/IP connections. Alternatively, if the host has multiple
         network addresses, you can use
         <option role="mysqld">--bind-address</option> to cause each
-        server to listen to a different address.)
+        server to listen to a different address.
       </para>
     </listitem>
 

@@ -268,90 +269,106 @@
     </para>
 
     <para>
-      There are different methods of creating a data directory for a new
-      instance:
+      There are different methods of setting up a data directory for a
+      new instance:
     </para>
 
     <itemizedlist>
 
       <listitem>
         <para>
-          Begin with a copy of an existing data directory. With this
-          method, any MySQL accounts or user data present in the data
-          directory are carried over to the new data directory.
+          Create a new data directory
         </para>
+      </listitem>
 
-        <orderedlist>
+      <listitem>
+        <para>
+          Copy an existing data directory
+        </para>
+      </listitem>
 
-          <listitem>
-            <para>
-              Stop the MySQL server using the data directory so that it
-              has a chance to flush any pending changes to disk.
-            </para>
-          </listitem>
+    </itemizedlist>
 
-          <listitem>
-            <para>
-              Copy the data directory to the location where the new data
-              directory should be.
-            </para>
-          </listitem>
+    <para>
+      The following discussion provides more detail about each method.
+    </para>
 
-          <listitem>
-            <para>
-              Copy the <filename>my.cnf</filename> or
-              <filename>my.ini</filename> option file used by the
-              existing server. This will serve as a basis for the new
-              instance.
-            </para>
-          </listitem>
+    <bridgehead>
+      Create a New Data Directory
+    </bridgehead>
 
-          <listitem>
-            <para>
-              Modify the new option file so that any pathnames referring
-              to the original data directory so that they refer to the
-              new data directory. Also, modify any other options that
-              must be unique per instances, such as the TCP/IP port
-              number and the log files. For a list of parameters that
-              must be unique per instance, see
-              <xref linkend="multiple-servers"/>.
-            </para>
-          </listitem>
+    <para>
+      With this method, the data directory will be in the same state as
+      when you first install MySQL. It will have the default set of
+      MySQL accounts and no user data.
+    </para>
 
-          <listitem>
-            <para>
-              Start the server, telling it to use the new option file.
-            </para>
-          </listitem>
+    <para>
+      On Unix, initialize the data directory by running
+      <command>mysql_install_db</command>. See
+      <xref linkend="unix-postinstallation"/>.
+    </para>
 
-        </orderedlist>
+    <para>
+      On Windows, the data directory is included with the MySQL
+      distribution. If you obtain a Windows Zip archive distribution,
+      you can unpack it into a temporary location, then copy the
+      <filename>data</filename> directory from this location to where
+      you are setting up the new instance.
+    </para>
+
+    <bridgehead>
+      Copy an Existing Data Directory
+    </bridgehead>
+
+    <para>
+      With this method, any MySQL accounts or user data present in the
+      data directory are carried over to the new data directory.
+    </para>
+
+    <orderedlist>
+
+      <listitem>
+        <para>
+          Stop the existing MySQL instance using the data directory so
+          that it has a chance to flush any pending changes to disk.
+        </para>
       </listitem>
 
       <listitem>
         <para>
-          Begin with a new data directory. With this method, the data
-          directory will be in the same state as when you first install
-          MySQL. It will have the default set of MySQL accounts and no
-          user data.
+          Copy the data directory to the location where the new data
+          directory should be.
         </para>
+      </listitem>
 
+      <listitem>
         <para>
-          On Unix, the data directory is initialized by running
-          <command>mysql_install_db</command>, so for a new instance,
-          use this program just as for a new install.
+          Copy the <filename>my.cnf</filename> or
+          <filename>my.ini</filename> option file used by the existing
+          instance. This serves as a basis for the new instance.
         </para>
+      </listitem>
 
+      <listitem>
         <para>
-          On Windows, the data directory is included with the
-          distribution. If you obtain a MySQL Windows Zip archive
-          distribution, you can unpack it into a temporary location,
-          then copy the <filename>data</filename> directory from this
-          location to where you are setting up the new instance.
+          Modify the new option file so that any pathnames referring to
+          the original data directory refer to the new data directory.
+          Also, modify any other options that must be unique per
+          instance, such as the TCP/IP port number and the log files.
+          For a list of parameters that must be unique per instance, see
+          <xref linkend="multiple-servers"/>.
         </para>
       </listitem>
 
-    </itemizedlist>
+      <listitem>
+        <para>
+          Start the new instance, telling it to use the new option file.
+        </para>
+      </listitem>
 
+    </orderedlist>
+
   </section>
 
   <section id="multiple-windows-servers">


Modified: trunk/refman-5.1/dba-multiple-servers.xml
===================================================================
--- trunk/refman-5.1/dba-multiple-servers.xml	2011-02-09 10:37:50 UTC (rev 25020)
+++ trunk/refman-5.1/dba-multiple-servers.xml	2011-02-09 15:33:36 UTC (rev 25021)
Changed blocks: 5, Lines Added: 78, Lines Deleted: 61; 7273 bytes

@@ -41,7 +41,7 @@
   </para>
 
   <para>
-    It is possible to use a different MySQL server binary per instances,
+    It is possible to use a different MySQL server binary per instance,
     or use the same binary for multiple instances, or any combination of
     the two approaches. For example, you might run a server from MySQL
     &previous-series; and one from MySQL &current-series;, to see how

@@ -57,7 +57,7 @@
     instances. Parameters can be set on the command line, in option
     files, or by setting environment variables. See
     <xref linkend="program-options"/>. To see the values used by a given
-    server, connect to it and execute a <literal role="stmt">SHOW
+    instance, connect to it and execute a <literal role="stmt">SHOW
     VARIABLES</literal> statement.
   </para>
 

@@ -66,7 +66,8 @@
     directory, and each instance should use a different data directory.
     The location is specified using the
     <option role="mysqld">--datadir=<replaceable>path</replaceable></option>
-    option.
+    option. For methods of configuring each instance with its own data
+    directory, see <xref linkend="multiple-data-directories"/>.
   </para>
 
   <warning>

@@ -111,10 +112,10 @@
 
       <para>
         <option role="mysqld">--port</option> controls the port number
-        for TCP/IP connections. (Alternatively, if the host has multiple
+        for TCP/IP connections. Alternatively, if the host has multiple
         network addresses, you can use
         <option role="mysqld">--bind-address</option> to cause each
-        server to listen to a different address.)
+        server to listen to a different address.
       </para>
     </listitem>
 

@@ -262,90 +263,106 @@
     </para>
 
     <para>
-      There are different methods of creating a data directory for a new
-      instance:
+      There are different methods of setting up a data directory for a
+      new instance:
     </para>
 
     <itemizedlist>
 
       <listitem>
         <para>
-          Begin with a copy of an existing data directory. With this
-          method, any MySQL accounts or user data present in the data
-          directory are carried over to the new data directory.
+          Create a new data directory
         </para>
+      </listitem>
 
-        <orderedlist>
+      <listitem>
+        <para>
+          Copy an existing data directory
+        </para>
+      </listitem>
 
-          <listitem>
-            <para>
-              Stop the MySQL server using the data directory so that it
-              has a chance to flush any pending changes to disk.
-            </para>
-          </listitem>
+    </itemizedlist>
 
-          <listitem>
-            <para>
-              Copy the data directory to the location where the new data
-              directory should be.
-            </para>
-          </listitem>
+    <para>
+      The following discussion provides more detail about each method.
+    </para>
 
-          <listitem>
-            <para>
-              Copy the <filename>my.cnf</filename> or
-              <filename>my.ini</filename> option file used by the
-              existing server. This will serve as a basis for the new
-              instance.
-            </para>
-          </listitem>
+    <bridgehead>
+      Create a New Data Directory
+    </bridgehead>
 
-          <listitem>
-            <para>
-              Modify the new option file so that any pathnames referring
-              to the original data directory so that they refer to the
-              new data directory. Also, modify any other options that
-              must be unique per instances, such as the TCP/IP port
-              number and the log files. For a list of parameters that
-              must be unique per instance, see
-              <xref linkend="multiple-servers"/>.
-            </para>
-          </listitem>
+    <para>
+      With this method, the data directory will be in the same state as
+      when you first install MySQL. It will have the default set of
+      MySQL accounts and no user data.
+    </para>
 
-          <listitem>
-            <para>
-              Start the server, telling it to use the new option file.
-            </para>
-          </listitem>
+    <para>
+      On Unix, initialize the data directory by running
+      <command>mysql_install_db</command>. See
+      <xref linkend="unix-postinstallation"/>.
+    </para>
 
-        </orderedlist>
+    <para>
+      On Windows, the data directory is included with the MySQL
+      distribution. If you obtain a Windows Zip archive distribution,
+      you can unpack it into a temporary location, then copy the
+      <filename>data</filename> directory from this location to where
+      you are setting up the new instance.
+    </para>
+
+    <bridgehead>
+      Copy an Existing Data Directory
+    </bridgehead>
+
+    <para>
+      With this method, any MySQL accounts or user data present in the
+      data directory are carried over to the new data directory.
+    </para>
+
+    <orderedlist>
+
+      <listitem>
+        <para>
+          Stop the existing MySQL instance using the data directory so
+          that it has a chance to flush any pending changes to disk.
+        </para>
       </listitem>
 
       <listitem>
         <para>
-          Begin with a new data directory. With this method, the data
-          directory will be in the same state as when you first install
-          MySQL. It will have the default set of MySQL accounts and no
-          user data.
+          Copy the data directory to the location where the new data
+          directory should be.
         </para>
+      </listitem>
 
+      <listitem>
         <para>
-          On Unix, the data directory is initialized by running
-          <command>mysql_install_db</command>, so for a new instance,
-          use this program just as for a new install.
+          Copy the <filename>my.cnf</filename> or
+          <filename>my.ini</filename> option file used by the existing
+          instance. This serves as a basis for the new instance.
         </para>
+      </listitem>
 
+      <listitem>
         <para>
-          On Windows, the data directory is included with the
-          distribution. If you obtain a MySQL Windows Zip archive
-          distribution, you can unpack it into a temporary location,
-          then copy the <filename>data</filename> directory from this
-          location to where you are setting up the new instance.
+          Modify the new option file so that any pathnames referring to
+          the original data directory refer to the new data directory.
+          Also, modify any other options that must be unique per
+          instance, such as the TCP/IP port number and the log files.
+          For a list of parameters that must be unique per instance, see
+          <xref linkend="multiple-servers"/>.
         </para>
       </listitem>
 
-    </itemizedlist>
+      <listitem>
+        <para>
+          Start the new instance, telling it to use the new option file.
+        </para>
+      </listitem>
 
+    </orderedlist>
+
   </section>
 
   <section id="multiple-windows-servers">


Modified: trunk/refman-5.5/dba-multiple-servers.xml
===================================================================
--- trunk/refman-5.5/dba-multiple-servers.xml	2011-02-09 10:37:50 UTC (rev 25020)
+++ trunk/refman-5.5/dba-multiple-servers.xml	2011-02-09 15:33:36 UTC (rev 25021)
Changed blocks: 5, Lines Added: 78, Lines Deleted: 61; 7273 bytes

@@ -41,7 +41,7 @@
   </para>
 
   <para>
-    It is possible to use a different MySQL server binary per instances,
+    It is possible to use a different MySQL server binary per instance,
     or use the same binary for multiple instances, or any combination of
     the two approaches. For example, you might run a server from MySQL
     &previous-series; and one from MySQL &current-series;, to see how

@@ -57,7 +57,7 @@
     instances. Parameters can be set on the command line, in option
     files, or by setting environment variables. See
     <xref linkend="program-options"/>. To see the values used by a given
-    server, connect to it and execute a <literal role="stmt">SHOW
+    instance, connect to it and execute a <literal role="stmt">SHOW
     VARIABLES</literal> statement.
   </para>
 

@@ -66,7 +66,8 @@
     directory, and each instance should use a different data directory.
     The location is specified using the
     <option role="mysqld">--datadir=<replaceable>path</replaceable></option>
-    option.
+    option. For methods of configuring each instance with its own data
+    directory, see <xref linkend="multiple-data-directories"/>.
   </para>
 
   <warning>

@@ -111,10 +112,10 @@
 
       <para>
         <option role="mysqld">--port</option> controls the port number
-        for TCP/IP connections. (Alternatively, if the host has multiple
+        for TCP/IP connections. Alternatively, if the host has multiple
         network addresses, you can use
         <option role="mysqld">--bind-address</option> to cause each
-        server to listen to a different address.)
+        server to listen to a different address.
       </para>
     </listitem>
 

@@ -262,90 +263,106 @@
     </para>
 
     <para>
-      There are different methods of creating a data directory for a new
-      instance:
+      There are different methods of setting up a data directory for a
+      new instance:
     </para>
 
     <itemizedlist>
 
       <listitem>
         <para>
-          Begin with a copy of an existing data directory. With this
-          method, any MySQL accounts or user data present in the data
-          directory are carried over to the new data directory.
+          Create a new data directory
         </para>
+      </listitem>
 
-        <orderedlist>
+      <listitem>
+        <para>
+          Copy an existing data directory
+        </para>
+      </listitem>
 
-          <listitem>
-            <para>
-              Stop the MySQL server using the data directory so that it
-              has a chance to flush any pending changes to disk.
-            </para>
-          </listitem>
+    </itemizedlist>
 
-          <listitem>
-            <para>
-              Copy the data directory to the location where the new data
-              directory should be.
-            </para>
-          </listitem>
+    <para>
+      The following discussion provides more detail about each method.
+    </para>
 
-          <listitem>
-            <para>
-              Copy the <filename>my.cnf</filename> or
-              <filename>my.ini</filename> option file used by the
-              existing server. This will serve as a basis for the new
-              instance.
-            </para>
-          </listitem>
+    <bridgehead>
+      Create a New Data Directory
+    </bridgehead>
 
-          <listitem>
-            <para>
-              Modify the new option file so that any pathnames referring
-              to the original data directory so that they refer to the
-              new data directory. Also, modify any other options that
-              must be unique per instances, such as the TCP/IP port
-              number and the log files. For a list of parameters that
-              must be unique per instance, see
-              <xref linkend="multiple-servers"/>.
-            </para>
-          </listitem>
+    <para>
+      With this method, the data directory will be in the same state as
+      when you first install MySQL. It will have the default set of
+      MySQL accounts and no user data.
+    </para>
 
-          <listitem>
-            <para>
-              Start the server, telling it to use the new option file.
-            </para>
-          </listitem>
+    <para>
+      On Unix, initialize the data directory by running
+      <command>mysql_install_db</command>. See
+      <xref linkend="unix-postinstallation"/>.
+    </para>
 
-        </orderedlist>
+    <para>
+      On Windows, the data directory is included with the MySQL
+      distribution. If you obtain a Windows Zip archive distribution,
+      you can unpack it into a temporary location, then copy the
+      <filename>data</filename> directory from this location to where
+      you are setting up the new instance.
+    </para>
+
+    <bridgehead>
+      Copy an Existing Data Directory
+    </bridgehead>
+
+    <para>
+      With this method, any MySQL accounts or user data present in the
+      data directory are carried over to the new data directory.
+    </para>
+
+    <orderedlist>
+
+      <listitem>
+        <para>
+          Stop the existing MySQL instance using the data directory so
+          that it has a chance to flush any pending changes to disk.
+        </para>
       </listitem>
 
       <listitem>
         <para>
-          Begin with a new data directory. With this method, the data
-          directory will be in the same state as when you first install
-          MySQL. It will have the default set of MySQL accounts and no
-          user data.
+          Copy the data directory to the location where the new data
+          directory should be.
         </para>
+      </listitem>
 
+      <listitem>
         <para>
-          On Unix, the data directory is initialized by running
-          <command>mysql_install_db</command>, so for a new instance,
-          use this program just as for a new install.
+          Copy the <filename>my.cnf</filename> or
+          <filename>my.ini</filename> option file used by the existing
+          instance. This serves as a basis for the new instance.
         </para>
+      </listitem>
 
+      <listitem>
         <para>
-          On Windows, the data directory is included with the
-          distribution. If you obtain a MySQL Windows Zip archive
-          distribution, you can unpack it into a temporary location,
-          then copy the <filename>data</filename> directory from this
-          location to where you are setting up the new instance.
+          Modify the new option file so that any pathnames referring to
+          the original data directory refer to the new data directory.
+          Also, modify any other options that must be unique per
+          instance, such as the TCP/IP port number and the log files.
+          For a list of parameters that must be unique per instance, see
+          <xref linkend="multiple-servers"/>.
         </para>
       </listitem>
 
-    </itemizedlist>
+      <listitem>
+        <para>
+          Start the new instance, telling it to use the new option file.
+        </para>
+      </listitem>
 
+    </orderedlist>
+
   </section>
 
   <section id="multiple-windows-servers">


Modified: trunk/refman-5.6/dba-multiple-servers.xml
===================================================================
--- trunk/refman-5.6/dba-multiple-servers.xml	2011-02-09 10:37:50 UTC (rev 25020)
+++ trunk/refman-5.6/dba-multiple-servers.xml	2011-02-09 15:33:36 UTC (rev 25021)
Changed blocks: 5, Lines Added: 78, Lines Deleted: 61; 7273 bytes

@@ -41,7 +41,7 @@
   </para>
 
   <para>
-    It is possible to use a different MySQL server binary per instances,
+    It is possible to use a different MySQL server binary per instance,
     or use the same binary for multiple instances, or any combination of
     the two approaches. For example, you might run a server from MySQL
     &previous-series; and one from MySQL &current-series;, to see how

@@ -57,7 +57,7 @@
     instances. Parameters can be set on the command line, in option
     files, or by setting environment variables. See
     <xref linkend="program-options"/>. To see the values used by a given
-    server, connect to it and execute a <literal role="stmt">SHOW
+    instance, connect to it and execute a <literal role="stmt">SHOW
     VARIABLES</literal> statement.
   </para>
 

@@ -66,7 +66,8 @@
     directory, and each instance should use a different data directory.
     The location is specified using the
     <option role="mysqld">--datadir=<replaceable>path</replaceable></option>
-    option.
+    option. For methods of configuring each instance with its own data
+    directory, see <xref linkend="multiple-data-directories"/>.
   </para>
 
   <warning>

@@ -111,10 +112,10 @@
 
       <para>
         <option role="mysqld">--port</option> controls the port number
-        for TCP/IP connections. (Alternatively, if the host has multiple
+        for TCP/IP connections. Alternatively, if the host has multiple
         network addresses, you can use
         <option role="mysqld">--bind-address</option> to cause each
-        server to listen to a different address.)
+        server to listen to a different address.
       </para>
     </listitem>
 

@@ -262,90 +263,106 @@
     </para>
 
     <para>
-      There are different methods of creating a data directory for a new
-      instance:
+      There are different methods of setting up a data directory for a
+      new instance:
     </para>
 
     <itemizedlist>
 
       <listitem>
         <para>
-          Begin with a copy of an existing data directory. With this
-          method, any MySQL accounts or user data present in the data
-          directory are carried over to the new data directory.
+          Create a new data directory
         </para>
+      </listitem>
 
-        <orderedlist>
+      <listitem>
+        <para>
+          Copy an existing data directory
+        </para>
+      </listitem>
 
-          <listitem>
-            <para>
-              Stop the MySQL server using the data directory so that it
-              has a chance to flush any pending changes to disk.
-            </para>
-          </listitem>
+    </itemizedlist>
 
-          <listitem>
-            <para>
-              Copy the data directory to the location where the new data
-              directory should be.
-            </para>
-          </listitem>
+    <para>
+      The following discussion provides more detail about each method.
+    </para>
 
-          <listitem>
-            <para>
-              Copy the <filename>my.cnf</filename> or
-              <filename>my.ini</filename> option file used by the
-              existing server. This will serve as a basis for the new
-              instance.
-            </para>
-          </listitem>
+    <bridgehead>
+      Create a New Data Directory
+    </bridgehead>
 
-          <listitem>
-            <para>
-              Modify the new option file so that any pathnames referring
-              to the original data directory so that they refer to the
-              new data directory. Also, modify any other options that
-              must be unique per instances, such as the TCP/IP port
-              number and the log files. For a list of parameters that
-              must be unique per instance, see
-              <xref linkend="multiple-servers"/>.
-            </para>
-          </listitem>
+    <para>
+      With this method, the data directory will be in the same state as
+      when you first install MySQL. It will have the default set of
+      MySQL accounts and no user data.
+    </para>
 
-          <listitem>
-            <para>
-              Start the server, telling it to use the new option file.
-            </para>
-          </listitem>
+    <para>
+      On Unix, initialize the data directory by running
+      <command>mysql_install_db</command>. See
+      <xref linkend="unix-postinstallation"/>.
+    </para>
 
-        </orderedlist>
+    <para>
+      On Windows, the data directory is included with the MySQL
+      distribution. If you obtain a Windows Zip archive distribution,
+      you can unpack it into a temporary location, then copy the
+      <filename>data</filename> directory from this location to where
+      you are setting up the new instance.
+    </para>
+
+    <bridgehead>
+      Copy an Existing Data Directory
+    </bridgehead>
+
+    <para>
+      With this method, any MySQL accounts or user data present in the
+      data directory are carried over to the new data directory.
+    </para>
+
+    <orderedlist>
+
+      <listitem>
+        <para>
+          Stop the existing MySQL instance using the data directory so
+          that it has a chance to flush any pending changes to disk.
+        </para>
       </listitem>
 
       <listitem>
         <para>
-          Begin with a new data directory. With this method, the data
-          directory will be in the same state as when you first install
-          MySQL. It will have the default set of MySQL accounts and no
-          user data.
+          Copy the data directory to the location where the new data
+          directory should be.
         </para>
+      </listitem>
 
+      <listitem>
         <para>
-          On Unix, the data directory is initialized by running
-          <command>mysql_install_db</command>, so for a new instance,
-          use this program just as for a new install.
+          Copy the <filename>my.cnf</filename> or
+          <filename>my.ini</filename> option file used by the existing
+          instance. This serves as a basis for the new instance.
         </para>
+      </listitem>
 
+      <listitem>
         <para>
-          On Windows, the data directory is included with the
-          distribution. If you obtain a MySQL Windows Zip archive
-          distribution, you can unpack it into a temporary location,
-          then copy the <filename>data</filename> directory from this
-          location to where you are setting up the new instance.
+          Modify the new option file so that any pathnames referring to
+          the original data directory refer to the new data directory.
+          Also, modify any other options that must be unique per
+          instance, such as the TCP/IP port number and the log files.
+          For a list of parameters that must be unique per instance, see
+          <xref linkend="multiple-servers"/>.
         </para>
       </listitem>
 
-    </itemizedlist>
+      <listitem>
+        <para>
+          Start the new instance, telling it to use the new option file.
+        </para>
+      </listitem>
 
+    </orderedlist>
+
   </section>
 
   <section id="multiple-windows-servers">


Modified: trunk/refman-6.0/dba-multiple-servers.xml
===================================================================
--- trunk/refman-6.0/dba-multiple-servers.xml	2011-02-09 10:37:50 UTC (rev 25020)
+++ trunk/refman-6.0/dba-multiple-servers.xml	2011-02-09 15:33:36 UTC (rev 25021)
Changed blocks: 5, Lines Added: 78, Lines Deleted: 61; 7273 bytes

@@ -41,7 +41,7 @@
   </para>
 
   <para>
-    It is possible to use a different MySQL server binary per instances,
+    It is possible to use a different MySQL server binary per instance,
     or use the same binary for multiple instances, or any combination of
     the two approaches. For example, you might run a server from MySQL
     &previous-series; and one from MySQL &current-series;, to see how

@@ -57,7 +57,7 @@
     instances. Parameters can be set on the command line, in option
     files, or by setting environment variables. See
     <xref linkend="program-options"/>. To see the values used by a given
-    server, connect to it and execute a <literal role="stmt">SHOW
+    instance, connect to it and execute a <literal role="stmt">SHOW
     VARIABLES</literal> statement.
   </para>
 

@@ -66,7 +66,8 @@
     directory, and each instance should use a different data directory.
     The location is specified using the
     <option role="mysqld">--datadir=<replaceable>path</replaceable></option>
-    option.
+    option. For methods of configuring each instance with its own data
+    directory, see <xref linkend="multiple-data-directories"/>.
   </para>
 
   <warning>

@@ -111,10 +112,10 @@
 
       <para>
         <option role="mysqld">--port</option> controls the port number
-        for TCP/IP connections. (Alternatively, if the host has multiple
+        for TCP/IP connections. Alternatively, if the host has multiple
         network addresses, you can use
         <option role="mysqld">--bind-address</option> to cause each
-        server to listen to a different address.)
+        server to listen to a different address.
       </para>
     </listitem>
 

@@ -262,90 +263,106 @@
     </para>
 
     <para>
-      There are different methods of creating a data directory for a new
-      instance:
+      There are different methods of setting up a data directory for a
+      new instance:
     </para>
 
     <itemizedlist>
 
       <listitem>
         <para>
-          Begin with a copy of an existing data directory. With this
-          method, any MySQL accounts or user data present in the data
-          directory are carried over to the new data directory.
+          Create a new data directory
         </para>
+      </listitem>
 
-        <orderedlist>
+      <listitem>
+        <para>
+          Copy an existing data directory
+        </para>
+      </listitem>
 
-          <listitem>
-            <para>
-              Stop the MySQL server using the data directory so that it
-              has a chance to flush any pending changes to disk.
-            </para>
-          </listitem>
+    </itemizedlist>
 
-          <listitem>
-            <para>
-              Copy the data directory to the location where the new data
-              directory should be.
-            </para>
-          </listitem>
+    <para>
+      The following discussion provides more detail about each method.
+    </para>
 
-          <listitem>
-            <para>
-              Copy the <filename>my.cnf</filename> or
-              <filename>my.ini</filename> option file used by the
-              existing server. This will serve as a basis for the new
-              instance.
-            </para>
-          </listitem>
+    <bridgehead>
+      Create a New Data Directory
+    </bridgehead>
 
-          <listitem>
-            <para>
-              Modify the new option file so that any pathnames referring
-              to the original data directory so that they refer to the
-              new data directory. Also, modify any other options that
-              must be unique per instances, such as the TCP/IP port
-              number and the log files. For a list of parameters that
-              must be unique per instance, see
-              <xref linkend="multiple-servers"/>.
-            </para>
-          </listitem>
+    <para>
+      With this method, the data directory will be in the same state as
+      when you first install MySQL. It will have the default set of
+      MySQL accounts and no user data.
+    </para>
 
-          <listitem>
-            <para>
-              Start the server, telling it to use the new option file.
-            </para>
-          </listitem>
+    <para>
+      On Unix, initialize the data directory by running
+      <command>mysql_install_db</command>. See
+      <xref linkend="unix-postinstallation"/>.
+    </para>
 
-        </orderedlist>
+    <para>
+      On Windows, the data directory is included with the MySQL
+      distribution. If you obtain a Windows Zip archive distribution,
+      you can unpack it into a temporary location, then copy the
+      <filename>data</filename> directory from this location to where
+      you are setting up the new instance.
+    </para>
+
+    <bridgehead>
+      Copy an Existing Data Directory
+    </bridgehead>
+
+    <para>
+      With this method, any MySQL accounts or user data present in the
+      data directory are carried over to the new data directory.
+    </para>
+
+    <orderedlist>
+
+      <listitem>
+        <para>
+          Stop the existing MySQL instance using the data directory so
+          that it has a chance to flush any pending changes to disk.
+        </para>
       </listitem>
 
       <listitem>
         <para>
-          Begin with a new data directory. With this method, the data
-          directory will be in the same state as when you first install
-          MySQL. It will have the default set of MySQL accounts and no
-          user data.
+          Copy the data directory to the location where the new data
+          directory should be.
         </para>
+      </listitem>
 
+      <listitem>
         <para>
-          On Unix, the data directory is initialized by running
-          <command>mysql_install_db</command>, so for a new instance,
-          use this program just as for a new install.
+          Copy the <filename>my.cnf</filename> or
+          <filename>my.ini</filename> option file used by the existing
+          instance. This serves as a basis for the new instance.
         </para>
+      </listitem>
 
+      <listitem>
         <para>
-          On Windows, the data directory is included with the
-          distribution. If you obtain a MySQL Windows Zip archive
-          distribution, you can unpack it into a temporary location,
-          then copy the <filename>data</filename> directory from this
-          location to where you are setting up the new instance.
+          Modify the new option file so that any pathnames referring to
+          the original data directory refer to the new data directory.
+          Also, modify any other options that must be unique per
+          instance, such as the TCP/IP port number and the log files.
+          For a list of parameters that must be unique per instance, see
+          <xref linkend="multiple-servers"/>.
         </para>
       </listitem>
 
-    </itemizedlist>
+      <listitem>
+        <para>
+          Start the new instance, telling it to use the new option file.
+        </para>
+      </listitem>
 
+    </orderedlist>
+
   </section>
 
   <section id="multiple-windows-servers">


Thread
svn commit - mysqldoc@docsrva: r25021 - in trunk: . refman-5.0 refman-5.1 refman-5.5 refman-5.6 refman-6.0paul.dubois9 Feb