List:Commits« Previous MessageNext Message »
From:paul Date:January 31 2006 3:55am
Subject:svn commit - mysqldoc@docsrva: r1144 - in trunk: . refman-4.1 refman-5.0 refman-5.1
View as plain text  
Author: paul
Date: 2006-01-31 04:55:49 +0100 (Tue, 31 Jan 2006)
New Revision: 1144

Log:
 r6963@frost:  paul | 2006-01-30 21:29:09 -0600
 General revisions.


Modified:
   trunk/
   trunk/refman-4.1/installing.xml
   trunk/refman-5.0/installing.xml
   trunk/refman-5.1/installing.xml


Property changes on: trunk
___________________________________________________________________
Name: svk:merge
   - b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:6962
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:2719
   + b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:6963
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:2719

Modified: trunk/refman-4.1/installing.xml
===================================================================
--- trunk/refman-4.1/installing.xml	2006-01-31 03:55:14 UTC (rev 1143)
+++ trunk/refman-4.1/installing.xml	2006-01-31 03:55:49 UTC (rev 1144)
@@ -11162,14 +11162,26 @@
         </indexterm>
 
         <para>
+          This section provides troubleshooting suggestions for problems
+          starting the server on Unix. If you are using Windows, see
+          <xref linkend="windows-troubleshooting"/>.
+        </para>
+
+        <para>
           If you have problems starting the server, here are some things
-          you can try:
+          to try:
         </para>
 
         <itemizedlist>
 
           <listitem>
             <para>
+              Check the error log to see why the server does not start.
+            </para>
+          </listitem>
+
+          <listitem>
+            <para>
               Specify any special options needed by the storage engines
               you are using.
             </para>
@@ -11184,21 +11196,15 @@
 
           <listitem>
             <para>
-              Make sure the server can use the data directory. The
-              ownership and permissions of the data directory and its
-              contents must be set such that the server can access and
+              Make sure that the server can access the data directory.
+              The ownership and permissions of the data directory and
+              its contents must be set such that the server can read and
               modify them.
             </para>
           </listitem>
 
           <listitem>
             <para>
-              Check the error log to see why the server does not start.
-            </para>
-          </listitem>
-
-          <listitem>
-            <para>
               Verify that the network interfaces the server wants to use
               are available.
             </para>
@@ -11208,12 +11214,12 @@
 
         <para>
           Some storage engines have options that control their behavior.
-          You can create a <filename>my.cnf</filename> file and set
-          startup options for the engines you plan to use. If you are
-          going to use storage engines that support transactional tables
-          (<literal>InnoDB</literal>, <literal>BDB</literal>), be sure
-          that you have them configured the way you want before starting
-          the server:
+          You can create a <filename>my.cnf</filename> file and specify
+          startup options for the engines that you plan to use. If you
+          are going to use storage engines that support transactional
+          tables (<literal>InnoDB</literal>, <literal>BDB</literal>,
+          <literal>NDB</literal>), be sure that you have them configured
+          the way you want before starting the server:
         </para>
 
         <itemizedlist>
@@ -11233,28 +11239,40 @@
           <listitem>
             <para>
               If you are using <literal>BDB</literal> (Berkeley DB)
-              tables, you should familiarize yourself with the different
-              <literal>BDB</literal>-specific startup options. See
-              <xref linkend="bdb-start"/>.
+              tables, see <xref linkend="bdb-start"/>.
             </para>
           </listitem>
 
+          <listitem>
+            <para>
+              If you are using MySQL Cluster, see
+              <xref linkend="mysql-cluster-configuration"/>.
+            </para>
+          </listitem>
+
         </itemizedlist>
 
         <para>
+          Storage engines will use default option values if you specify
+          none, but it is recommended that you review the available
+          options and specify explicit values for those for which the
+          defaults are not appropriate for your installation.
+        </para>
+
+        <para>
           When the <command>mysqld</command> server starts, it changes
           location to the data directory. This is where it expects to
-          find databases and where it expects to write log files. On
-          Unix, the server also writes the pid (process ID) file in the
-          data directory.
+          find databases and where it expects to write log files. The
+          server also writes the pid (process ID) file in the data
+          directory.
         </para>
 
         <para>
           The data directory location is hardwired in when the server is
           compiled. This is where the server looks for the data
           directory by default. If the data directory is located
-          somewhere else on your system, the server does not work
-          properly. You can find out what the default path settings are
+          somewhere else on your system, the server will not work
+          properly. You can determine what the default path settings are
           by invoking <command>mysqld</command> with the
           <option>--verbose</option> and <option>--help</option>
           options. (Prior to MySQL 4.1, omit the
@@ -11262,11 +11280,11 @@
         </para>
 
         <para>
-          If the defaults do not match the MySQL installation layout on
-          your system, you can override them by specifying options on
-          the command line to <command>mysqld</command> or
-          <command>mysqld_safe</command>. You can also list the options
-          in an option file.
+          If the default locations don't match the MySQL installation
+          layout on your system, you can override them by specifying
+          options to <command>mysqld</command> or
+          <command>mysqld_safe</command> on the command line or in an
+          option file.
         </para>
 
         <para>
@@ -11283,7 +11301,7 @@
           <command>mysqld</command> with those options followed by the
           <option>--verbose</option> and <option>--help</option>
           options. For example, if you change location into the
-          directory where <command>mysqld</command> is installed, and
+          directory where <command>mysqld</command> is installed and
           then run the following command, it shows the effect of
           starting the server with a base directory of
           <filename>/usr/local</filename>:
@@ -11333,13 +11351,13 @@
         <para>
           If you get <literal>Errcode 13</literal> (which means
           <literal>Permission denied</literal>) when starting
-          <command>mysqld</command>, this means that the access
-          privileges of the data directory or its contents do not allow
-          the server access. In this case, you must change the
-          permissions for the files and directories involved so that the
-          server has the right to use them. You can also start the
-          server as <literal>root</literal>, but this can raise security
-          issues and thus should be avoided.
+          <command>mysqld</command>, this means that the privileges of
+          the data directory or its contents do not allow the server
+          access. In this case, you change the permissions for the
+          involved files and directories so that the server has the
+          right to use them. You can also start the server as
+          <literal>root</literal>, but this raises security issues and
+          should be avoided.
         </para>
 
         <para>
@@ -11355,8 +11373,9 @@
 
         <para>
           If the data directory or its files or subdirectories are not
-          owned by the account that you use for running the server,
-          change their ownership to that account:
+          owned by the login account that you use for running the
+          server, change their ownership to that account. If the account
+          is named <literal>mysql</literal>, use these commands:
         </para>
 
 <programlisting>
@@ -11365,9 +11384,8 @@
 </programlisting>
 
         <para>
-          If the server fails to start up correctly, check the error log
-          file to see whether you can find out why. Log files are
-          located in the data directory (typically
+          If the server fails to start up correctly, check the error
+          log. Log files are located in the data directory (typically
           <filename>C:\mysql\data</filename> on Windows,
           <filename>/usr/local/mysql/data</filename> for a Unix binary
           distribution, and <filename>/usr/local/var</filename> for a
@@ -11389,9 +11407,9 @@
 </programlisting>
 
         <para>
-          The error log contains information that indicates why the
-          server couldn't start. For example, you might see something
-          like this in the log:
+          The error log should contain information that indicates why
+          the server couldn't start. For example, you might see
+          something like this in the log:
         </para>
 
 <programlisting>
@@ -11447,18 +11465,18 @@
 
         <para>
           If no other server is running, try to execute the command
-          <command>telnet <replaceable>your-host-name</replaceable>
-          <replaceable>tcp-ip-port-number</replaceable></command>. (The
-          default MySQL port number is 3306.) Then press
-          <keycap>Enter</keycap> a couple of times. If you do not get an
-          error message like <literal>telnet: Unable to connect to
-          remote host: Connection refused</literal>, some other program
-          is using the TCP/IP port that <command>mysqld</command> is
-          trying to use. You will need to track down what program this
-          is and disable it, or else to tell <command>mysqld</command>
-          to listen on a different port with the <option>--port</option>
-          option. In this case, you also need to specify the port number
-          for client programs when connecting to the server via TCP/IP.
+          <literal>telnet <replaceable>your_host_name</replaceable>
+          <replaceable>tcp_ip_port_number</replaceable></literal>. (The
+          default MySQL port number is 3306.) Then press Enter a couple
+          of times. If you don't get an error message like
+          <literal>telnet: Unable to connect to remote host: Connection
+          refused</literal>, some other program is using the TCP/IP port
+          that <command>mysqld</command> is trying to use. You'll need
+          need to track down what program this is and disable it, or
+          else to tell <command>mysqld</command> to listen on a
+          different port with the <option>--port</option> option. In
+          this case, you also need to specify the port number for client
+          programs when connecting to the server via TCP/IP.
         </para>
 
         <para>
@@ -11490,11 +11508,6 @@
           <xref linkend="making-trace-files"/>.
         </para>
 
-        <para>
-          See <xref linkend="windows-troubleshooting"/>, for more
-          information on troubleshooting Windows installations.
-        </para>
-
       </section>
 
     </section>
@@ -11547,7 +11560,8 @@
 
       <para>
         Part of the MySQL installation process is to set up the
-        <literal>mysql</literal> database containing the grant tables:
+        <literal>mysql</literal> database that contains the grant
+        tables:
       </para>
 
       <itemizedlist>
@@ -11611,8 +11625,8 @@
                 On Unix, both <literal>root</literal> accounts are for
                 connections from the local host. Connections must be
                 made from the local host by specifying a hostname of
-                <literal>localhost</literal> for one account, or the
-                actual hostname or IP number for the other.
+                <literal>localhost</literal> for one of the accounts, or
+                the actual hostname or IP number for the other.
               </para>
             </listitem>
 
@@ -11626,8 +11640,8 @@
         <listitem>
           <para>
             Two anonymous-user accounts are created, each with an empty
-            username. The anonymous accounts have no passwords, so
-            anyone can use them to connect to the MySQL server.
+            username. The anonymous accounts have no password, so anyone
+            can use them to connect to the MySQL server.
           </para>
 
           <itemizedlist>
@@ -11638,8 +11652,8 @@
                 from the local host. It has all privileges, just like
                 the <literal>root</literal> accounts. The other is for
                 connections from any host and has all privileges for the
-                <literal>test</literal> database or other databases with
-                names that start with <literal>test</literal>.
+                <literal>test</literal> database and for other databases
+                with names that start with <literal>test</literal>.
               </para>
             </listitem>
 
@@ -11648,11 +11662,11 @@
                 On Unix, both anonymous accounts are for connections
                 from the local host. Connections must be made from the
                 local host by specifying a hostname of
-                <literal>localhost</literal> for one account, or the
-                actual hostname or IP number for the other. These
+                <literal>localhost</literal> for one of the accounts, or
+                the actual hostname or IP number for the other. These
                 accounts have all privileges for the
-                <literal>test</literal> database or other databases with
-                names that start with <literal>test_</literal>.
+                <literal>test</literal> database and for other databases
+                with names that start with <literal>test_</literal>.
               </para>
             </listitem>
 
@@ -11672,14 +11686,15 @@
         <listitem>
           <para>
             If you want to prevent clients from connecting as anonymous
-            users without a password, you should either assign passwords
-            to the anonymous accounts or else remove them.
+            users without a password, you should either assign a
+            password to each anonymous account or else remove the
+            accounts.
           </para>
         </listitem>
 
         <listitem>
           <para>
-            You should assign passwords to the MySQL
+            You should assign a password to each MySQL
             <literal>root</literal> accounts.
           </para>
         </listitem>
@@ -11698,16 +11713,17 @@
 
       <para>
         You might want to defer setting the passwords until later, so
-        that you do not need to specify them while you perform
-        additional setup or testing. However, be sure to set them before
-        using your installation for any real production work.
+        that you don't need to specify them while you perform additional
+        setup or testing. However, be sure to set them before using your
+        installation for production purposes.
       </para>
 
       <para>
-        To assign passwords to the anonymous accounts, you can use
-        either <literal>SET PASSWORD</literal> or
-        <literal>UPDATE</literal>. In both cases, be sure to encrypt the
-        password using the <literal>PASSWORD()</literal> function.
+        To assign passwords to the anonymous accounts, connect to the
+        server as <literal>root</literal> and then either <literal>SET
+        PASSWORD</literal> or <literal>UPDATE</literal>. In either case,
+        be sure to encrypt the password using the
+        <literal>PASSWORD()</literal> function.
       </para>
 
       <para>
@@ -11805,7 +11821,7 @@
 </programlisting>
 
       <para>
-        This account allows anonymous access but has full privileges, so
+        That account allows anonymous access but has full privileges, so
         removing it improves security.
       </para>
 
@@ -11928,19 +11944,20 @@
 
 <programlisting>
 shell&gt; <userinput>mysqladmin -u root -p shutdown</userinput>
-Enter password: (enter root password here)
+<replaceable>Enter password: (enter root password here)</replaceable>
 </programlisting>
 
       <para>
         <emphasis role="bold">Note</emphasis>: If you forget your
-        <literal>root</literal> password after setting it up, the
-        procedure for resetting it is covered in
-        <xref linkend="resetting-permissions"/>.
+        <literal>root</literal> password after setting it up,
+        <xref linkend="resetting-permissions"/>, covers the procedure
+        for resetting it.
       </para>
 
       <para>
-        To set up new accounts, you can use the <literal>GRANT</literal>
-        statement. For instructions, see <xref linkend="adding-users"/>.
+        To set up additional accounts, you can use the
+        <literal>GRANT</literal> statement. For instructions, see
+        <xref linkend="adding-users"/>.
       </para>
 
     </section>

Modified: trunk/refman-5.0/installing.xml
===================================================================
--- trunk/refman-5.0/installing.xml	2006-01-31 03:55:14 UTC (rev 1143)
+++ trunk/refman-5.0/installing.xml	2006-01-31 03:55:49 UTC (rev 1144)
@@ -10994,14 +10994,26 @@
         </indexterm>
 
         <para>
+          This section provides troubleshooting suggestions for problems
+          starting the server on Unix. If you are using Windows, see
+          <xref linkend="windows-troubleshooting"/>.
+        </para>
+
+        <para>
           If you have problems starting the server, here are some things
-          you can try:
+          to try:
         </para>
 
         <itemizedlist>
 
           <listitem>
             <para>
+              Check the error log to see why the server does not start.
+            </para>
+          </listitem>
+
+          <listitem>
+            <para>
               Specify any special options needed by the storage engines
               you are using.
             </para>
@@ -11016,21 +11028,15 @@
 
           <listitem>
             <para>
-              Make sure the server can use the data directory. The
-              ownership and permissions of the data directory and its
-              contents must be set such that the server can access and
+              Make sure that the server can access the data directory.
+              The ownership and permissions of the data directory and
+              its contents must be set such that the server can read and
               modify them.
             </para>
           </listitem>
 
           <listitem>
             <para>
-              Check the error log to see why the server does not start.
-            </para>
-          </listitem>
-
-          <listitem>
-            <para>
               Verify that the network interfaces the server wants to use
               are available.
             </para>
@@ -11040,22 +11046,19 @@
 
         <para>
           Some storage engines have options that control their behavior.
-          You can create a <filename>my.cnf</filename> file and set
-          startup options for the engines you plan to use. If you are
-          going to use storage engines that support transactional tables
-          (<literal>InnoDB</literal>, <literal>BDB</literal>), be sure
-          that you have them configured the way you want before starting
-          the server:
+          You can create a <filename>my.cnf</filename> file and specify
+          startup options for the engines that you plan to use. If you
+          are going to use storage engines that support transactional
+          tables (<literal>InnoDB</literal>, <literal>BDB</literal>,
+          <literal>NDB</literal>), be sure that you have them configured
+          the way you want before starting the server:
         </para>
 
         <itemizedlist>
 
           <listitem>
             <para>
-              If you are using <literal>InnoDB</literal> tables, refer
-              to the <literal>InnoDB</literal>-specific startup options.
-              <literal>InnoDB</literal> uses default values for its
-              configuration options if you specify none. See
+              If you are using <literal>InnoDB</literal> tables, see
               <xref linkend="innodb-configuration"/>.
             </para>
           </listitem>
@@ -11063,39 +11066,51 @@
           <listitem>
             <para>
               If you are using <literal>BDB</literal> (Berkeley DB)
-              tables, you should familiarize yourself with the different
-              <literal>BDB</literal>-specific startup options. See
-              <xref linkend="bdb-start"/>.
+              tables, see <xref linkend="bdb-start"/>.
             </para>
           </listitem>
 
+          <listitem>
+            <para>
+              If you are using MySQL Cluster, see
+              <xref linkend="mysql-cluster-configuration"/>.
+            </para>
+          </listitem>
+
         </itemizedlist>
 
         <para>
+          Storage engines will use default option values if you specify
+          none, but it is recommended that you review the available
+          options and specify explicit values for those for which the
+          defaults are not appropriate for your installation.
+        </para>
+
+        <para>
           When the <command>mysqld</command> server starts, it changes
           location to the data directory. This is where it expects to
-          find databases and where it expects to write log files. On
-          Unix, the server also writes the pid (process ID) file in the
-          data directory.
+          find databases and where it expects to write log files. The
+          server also writes the pid (process ID) file in the data
+          directory.
         </para>
 
         <para>
           The data directory location is hardwired in when the server is
           compiled. This is where the server looks for the data
           directory by default. If the data directory is located
-          somewhere else on your system, the server does not work
-          properly. You can find out what the default path settings are
+          somewhere else on your system, the server will not work
+          properly. You can determine what the default path settings are
           by invoking <command>mysqld</command> with the
           <option>--verbose</option> and <option>--help</option>
           options.
         </para>
 
         <para>
-          If the defaults don't match the MySQL installation layout on
-          your system, you can override them by specifying options on
-          the command line to <command>mysqld</command> or
-          <command>mysqld_safe</command>. You can also list the options
-          in an option file.
+          If the default locations don't match the MySQL installation
+          layout on your system, you can override them by specifying
+          options to <command>mysqld</command> or
+          <command>mysqld_safe</command> on the command line or in an
+          option file.
         </para>
 
         <para>
@@ -11112,7 +11127,7 @@
           <command>mysqld</command> with those options followed by the
           <option>--verbose</option> and <option>--help</option>
           options. For example, if you change location into the
-          directory where <command>mysqld</command> is installed, and
+          directory where <command>mysqld</command> is installed and
           then run the following command, it shows the effect of
           starting the server with a base directory of
           <filename>/usr/local</filename>:
@@ -11161,13 +11176,13 @@
         <para>
           If you get <literal>Errcode 13</literal> (which means
           <literal>Permission denied</literal>) when starting
-          <command>mysqld</command>, this means that the access
-          privileges of the data directory or its contents do not allow
-          the server access. In this case, you change the permissions
-          for the involved files and directories so that the server has
-          the right to use them. You can also start the server as
-          <literal>root</literal>, but this can raise security issues
-          and should be avoided.
+          <command>mysqld</command>, this means that the privileges of
+          the data directory or its contents do not allow the server
+          access. In this case, you change the permissions for the
+          involved files and directories so that the server has the
+          right to use them. You can also start the server as
+          <literal>root</literal>, but this raises security issues and
+          should be avoided.
         </para>
 
         <para>
@@ -11183,8 +11198,9 @@
 
         <para>
           If the data directory or its files or subdirectories are not
-          owned by the account that you use for running the server,
-          change their ownership to that account:
+          owned by the login account that you use for running the
+          server, change their ownership to that account. If the account
+          is named <literal>mysql</literal>, use these commands:
         </para>
 
 <programlisting>
@@ -11199,14 +11215,14 @@
         </remark>
 
         <para>
-          If the server fails to start up correctly, check the error log
-          file to see whether you can find out why. Log files are
-          located in the data directory (typically <filename>C:\Program
-          Files\MySQL\MySQL Server &current-series;\data</filename> on
-          Windows, <filename>/usr/local/mysql/data</filename> for a Unix
-          binary distribution, and <filename>/usr/local/var</filename>
-          for a Unix source distribution). Look in the data directory
-          for files with names of the form
+          If the server fails to start up correctly, check the error
+          log. Log files are located in the data directory (typically
+          <filename>C:\Program Files\MySQL\MySQL Server
+          &current-series;\data</filename> on Windows,
+          <filename>/usr/local/mysql/data</filename> for a Unix binary
+          distribution, and <filename>/usr/local/var</filename> for a
+          Unix source distribution). Look in the data directory for
+          files with names of the form
           <filename><replaceable>host_name</replaceable>.err</filename>
           and
           <filename><replaceable>host_name</replaceable>.log</filename>,
@@ -11221,9 +11237,9 @@
 </programlisting>
 
         <para>
-          The error log contains information that indicates why the
-          server couldn't start. For example, you might see something
-          like this in the log:
+          The error log should contain information that indicates why
+          the server couldn't start. For example, you might see
+          something like this in the log:
         </para>
 
 <programlisting>
@@ -11279,9 +11295,10 @@
 
         <para>
           If no other server is running, try to execute the command
-          <literal>telnet your-host-name tcp-ip-port-number</literal>.
-          (The default MySQL port number is 3306.) Then press Enter a
-          couple of times. If you don't get an error message like
+          <literal>telnet <replaceable>your_host_name</replaceable>
+          <replaceable>tcp_ip_port_number</replaceable></literal>. (The
+          default MySQL port number is 3306.) Then press Enter a couple
+          of times. If you don't get an error message like
           <literal>telnet: Unable to connect to remote host: Connection
           refused</literal>, some other program is using the TCP/IP port
           that <command>mysqld</command> is trying to use. You'll need
@@ -11321,11 +11338,6 @@
           <xref linkend="making-trace-files"/>.
         </para>
 
-        <para>
-          See <xref linkend="windows-troubleshooting"/>, for more
-          information on troubleshooting Windows installations.
-        </para>
-
       </section>
 
     </section>
@@ -11378,7 +11390,8 @@
 
       <para>
         Part of the MySQL installation process is to set up the
-        <literal>mysql</literal> database containing the grant tables:
+        <literal>mysql</literal> database that contains the grant
+        tables:
       </para>
 
       <itemizedlist>
@@ -11438,8 +11451,8 @@
                 On Unix, both <literal>root</literal> accounts are for
                 connections from the local host. Connections must be
                 made from the local host by specifying a hostname of
-                <literal>localhost</literal> for one account, or the
-                actual hostname or IP number for the other.
+                <literal>localhost</literal> for one of the accounts, or
+                the actual hostname or IP number for the other.
               </para>
             </listitem>
 
@@ -11453,8 +11466,8 @@
         <listitem>
           <para>
             Two anonymous-user accounts are created, each with an empty
-            username. The anonymous accounts have no passwords, so
-            anyone can use them to connect to the MySQL server.
+            username. The anonymous accounts have no password, so anyone
+            can use them to connect to the MySQL server.
           </para>
 
           <itemizedlist>
@@ -11465,8 +11478,8 @@
                 from the local host. It has all privileges, just like
                 the <literal>root</literal> accounts. The other is for
                 connections from any host and has all privileges for the
-                <literal>test</literal> database or other databases with
-                names that start with <literal>test</literal>.
+                <literal>test</literal> database and for other databases
+                with names that start with <literal>test</literal>.
               </para>
             </listitem>
 
@@ -11475,11 +11488,11 @@
                 On Unix, both anonymous accounts are for connections
                 from the local host. Connections must be made from the
                 local host by specifying a hostname of
-                <literal>localhost</literal> for one account, or the
-                actual hostname or IP number for the other. These
+                <literal>localhost</literal> for one of the accounts, or
+                the actual hostname or IP number for the other. These
                 accounts have all privileges for the
-                <literal>test</literal> database or other databases with
-                names that start with <literal>test_</literal>.
+                <literal>test</literal> database and for other databases
+                with names that start with <literal>test_</literal>.
               </para>
             </listitem>
 
@@ -11499,14 +11512,15 @@
         <listitem>
           <para>
             If you want to prevent clients from connecting as anonymous
-            users without a password, you should either assign passwords
-            to the anonymous accounts or else remove them.
+            users without a password, you should either assign a
+            password to each anonymous account or else remove the
+            accounts.
           </para>
         </listitem>
 
         <listitem>
           <para>
-            You should assign passwords to the MySQL
+            You should assign a password to each MySQL
             <literal>root</literal> accounts.
           </para>
         </listitem>
@@ -11527,14 +11541,15 @@
         You might want to defer setting the passwords until later, so
         that you don't need to specify them while you perform additional
         setup or testing. However, be sure to set them before using your
-        installation for any real production work.
+        installation for production purposes.
       </para>
 
       <para>
-        To assign passwords to the anonymous accounts, you can use
-        either <literal>SET PASSWORD</literal> or
-        <literal>UPDATE</literal>. In both cases, be sure to encrypt the
-        password using the <literal>PASSWORD()</literal> function.
+        To assign passwords to the anonymous accounts, connect to the
+        server as <literal>root</literal> and then either <literal>SET
+        PASSWORD</literal> or <literal>UPDATE</literal>. In either case,
+        be sure to encrypt the password using the
+        <literal>PASSWORD()</literal> function.
       </para>
 
       <para>
@@ -11632,7 +11647,7 @@
 </programlisting>
 
       <para>
-        This account allows anonymous access but has full privileges, so
+        That account allows anonymous access but has full privileges, so
         removing it improves security.
       </para>
 
@@ -11706,8 +11721,8 @@
       </para>
 
 <programlisting>
-shell&gt; mysqladmin -u root password "<replaceable>newpwd</replaceable>"
-shell&gt; mysqladmin -u root -h <replaceable>host_name</replaceable> password "<replaceable>newpwd</replaceable>"
+shell&gt; <userinput>mysqladmin -u root password "<replaceable>newpwd</replaceable>"</userinput>
+shell&gt; <userinput>mysqladmin -u root -h <replaceable>host_name</replaceable> password "<replaceable>newpwd</replaceable>"</userinput>
 </programlisting>
 
       <para>
@@ -11747,19 +11762,20 @@
 
 <programlisting>
 shell&gt; <userinput>mysqladmin -u root -p shutdown</userinput>
-Enter password: <userinput>(enter root password here)</userinput>
+Enter password: <replaceable>(enter root password here)</replaceable>
 </programlisting>
 
       <para>
         <emphasis role="bold">Note</emphasis>: If you forget your
-        <literal>root</literal> password after setting it up, the
-        procedure for resetting it is covered in
-        <xref linkend="resetting-permissions"/>.
+        <literal>root</literal> password after setting it up,
+        <xref linkend="resetting-permissions"/>, covers the procedure
+        for resetting it.
       </para>
 
       <para>
-        To set up new accounts, you can use the <literal>GRANT</literal>
-        statement. For instructions, see <xref linkend="adding-users"/>.
+        To set up additional accounts, you can use the
+        <literal>GRANT</literal> statement. For instructions, see
+        <xref linkend="adding-users"/>.
       </para>
 
     </section>

Modified: trunk/refman-5.1/installing.xml
===================================================================
--- trunk/refman-5.1/installing.xml	2006-01-31 03:55:14 UTC (rev 1143)
+++ trunk/refman-5.1/installing.xml	2006-01-31 03:55:49 UTC (rev 1144)
@@ -10990,14 +10990,26 @@
         </indexterm>
 
         <para>
+          This section provides troubleshooting suggestions for problems
+          starting the server on Unix. If you are using Windows, see
+          <xref linkend="windows-troubleshooting"/>.
+        </para>
+
+        <para>
           If you have problems starting the server, here are some things
-          you can try:
+          to try:
         </para>
 
         <itemizedlist>
 
           <listitem>
             <para>
+              Check the error log to see why the server does not start.
+            </para>
+          </listitem>
+
+          <listitem>
+            <para>
               Specify any special options needed by the storage engines
               you are using.
             </para>
@@ -11012,21 +11024,15 @@
 
           <listitem>
             <para>
-              Make sure the server can use the data directory. The
-              ownership and permissions of the data directory and its
-              contents must be set such that the server can access and
+              Make sure that the server can access the data directory.
+              The ownership and permissions of the data directory and
+              its contents must be set such that the server can read and
               modify them.
             </para>
           </listitem>
 
           <listitem>
             <para>
-              Check the error log to see why the server does not start.
-            </para>
-          </listitem>
-
-          <listitem>
-            <para>
               Verify that the network interfaces the server wants to use
               are available.
             </para>
@@ -11036,22 +11042,19 @@
 
         <para>
           Some storage engines have options that control their behavior.
-          You can create a <filename>my.cnf</filename> file and set
-          startup options for the engines you plan to use. If you are
-          going to use storage engines that support transactional tables
-          (<literal>InnoDB</literal>, <literal>BDB</literal>), be sure
-          that you have them configured the way you want before starting
-          the server:
+          You can create a <filename>my.cnf</filename> file and specify
+          startup options for the engines that you plan to use. If you
+          are going to use storage engines that support transactional
+          tables (<literal>InnoDB</literal>, <literal>BDB</literal>,
+          <literal>NDB</literal>), be sure that you have them configured
+          the way you want before starting the server:
         </para>
 
         <itemizedlist>
 
           <listitem>
             <para>
-              If you are using <literal>InnoDB</literal> tables, refer
-              to the <literal>InnoDB</literal>-specific startup options.
-              <literal>InnoDB</literal> uses default values for its
-              configuration options if you specify none. See
+              If you are using <literal>InnoDB</literal> tables, see
               <xref linkend="innodb-configuration"/>.
             </para>
           </listitem>
@@ -11059,39 +11062,51 @@
           <listitem>
             <para>
               If you are using <literal>BDB</literal> (Berkeley DB)
-              tables, you should familiarize yourself with the different
-              <literal>BDB</literal>-specific startup options. See
-              <xref linkend="bdb-start"/>.
+              tables, see <xref linkend="bdb-start"/>.
             </para>
           </listitem>
 
+          <listitem>
+            <para>
+              If you are using MySQL Cluster, see
+              <xref linkend="mysql-cluster-configuration"/>.
+            </para>
+          </listitem>
+
         </itemizedlist>
 
         <para>
+          Storage engines will use default option values if you specify
+          none, but it is recommended that you review the available
+          options and specify explicit values for those for which the
+          defaults are not appropriate for your installation.
+        </para>
+
+        <para>
           When the <command>mysqld</command> server starts, it changes
           location to the data directory. This is where it expects to
-          find databases and where it expects to write log files. On
-          Unix, the server also writes the pid (process ID) file in the
-          data directory.
+          find databases and where it expects to write log files. The
+          server also writes the pid (process ID) file in the data
+          directory.
         </para>
 
         <para>
           The data directory location is hardwired in when the server is
           compiled. This is where the server looks for the data
           directory by default. If the data directory is located
-          somewhere else on your system, the server does not work
-          properly. You can find out what the default path settings are
+          somewhere else on your system, the server will not work
+          properly. You can determine what the default path settings are
           by invoking <command>mysqld</command> with the
           <option>--verbose</option> and <option>--help</option>
           options.
         </para>
 
         <para>
-          If the defaults don't match the MySQL installation layout on
-          your system, you can override them by specifying options on
-          the command line to <command>mysqld</command> or
-          <command>mysqld_safe</command>. You can also list the options
-          in an option file.
+          If the default locations don't match the MySQL installation
+          layout on your system, you can override them by specifying
+          options to <command>mysqld</command> or
+          <command>mysqld_safe</command> on the command line or in an
+          option file.
         </para>
 
         <para>
@@ -11108,7 +11123,7 @@
           <command>mysqld</command> with those options followed by the
           <option>--verbose</option> and <option>--help</option>
           options. For example, if you change location into the
-          directory where <command>mysqld</command> is installed, and
+          directory where <command>mysqld</command> is installed and
           then run the following command, it shows the effect of
           starting the server with a base directory of
           <filename>/usr/local</filename>:
@@ -11157,13 +11172,13 @@
         <para>
           If you get <literal>Errcode 13</literal> (which means
           <literal>Permission denied</literal>) when starting
-          <command>mysqld</command>, this means that the access
-          privileges of the data directory or its contents do not allow
-          the server access. In this case, you change the permissions
-          for the involved files and directories so that the server has
-          the right to use them. You can also start the server as
-          <literal>root</literal>, but this can raise security issues
-          and should be avoided.
+          <command>mysqld</command>, this means that the privileges of
+          the data directory or its contents do not allow the server
+          access. In this case, you change the permissions for the
+          involved files and directories so that the server has the
+          right to use them. You can also start the server as
+          <literal>root</literal>, but this raises security issues and
+          should be avoided.
         </para>
 
         <para>
@@ -11179,8 +11194,9 @@
 
         <para>
           If the data directory or its files or subdirectories are not
-          owned by the account that you use for running the server,
-          change their ownership to that account:
+          owned by the login account that you use for running the
+          server, change their ownership to that account. If the account
+          is named <literal>mysql</literal>, use these commands:
         </para>
 
 <programlisting>
@@ -11195,14 +11211,14 @@
         </remark>
 
         <para>
-          If the server fails to start up correctly, check the error log
-          file to see whether you can find out why. Log files are
-          located in the data directory (typically <filename>C:\Program
-          Files\MySQL\MySQL Server &current-series;\data</filename> on
-          Windows, <filename>/usr/local/mysql/data</filename> for a Unix
-          binary distribution, and <filename>/usr/local/var</filename>
-          for a Unix source distribution). Look in the data directory
-          for files with names of the form
+          If the server fails to start up correctly, check the error
+          log. Log files are located in the data directory (typically
+          <filename>C:\Program Files\MySQL\MySQL Server
+          &current-series;\data</filename> on Windows,
+          <filename>/usr/local/mysql/data</filename> for a Unix binary
+          distribution, and <filename>/usr/local/var</filename> for a
+          Unix source distribution). Look in the data directory for
+          files with names of the form
           <filename><replaceable>host_name</replaceable>.err</filename>
           and
           <filename><replaceable>host_name</replaceable>.log</filename>,
@@ -11217,9 +11233,9 @@
 </programlisting>
 
         <para>
-          The error log contains information that indicates why the
-          server couldn't start. For example, you might see something
-          like this in the log:
+          The error log should contain information that indicates why
+          the server couldn't start. For example, you might see
+          something like this in the log:
         </para>
 
 <programlisting>
@@ -11275,9 +11291,10 @@
 
         <para>
           If no other server is running, try to execute the command
-          <literal>telnet your-host-name tcp-ip-port-number</literal>.
-          (The default MySQL port number is 3306.) Then press Enter a
-          couple of times. If you don't get an error message like
+          <literal>telnet <replaceable>your_host_name</replaceable>
+          <replaceable>tcp_ip_port_number</replaceable></literal>. (The
+          default MySQL port number is 3306.) Then press Enter a couple
+          of times. If you don't get an error message like
           <literal>telnet: Unable to connect to remote host: Connection
           refused</literal>, some other program is using the TCP/IP port
           that <command>mysqld</command> is trying to use. You'll need
@@ -11317,11 +11334,6 @@
           <xref linkend="making-trace-files"/>.
         </para>
 
-        <para>
-          See <xref linkend="windows-troubleshooting"/>, for more
-          information on troubleshooting Windows installations.
-        </para>
-
       </section>
 
     </section>
@@ -11374,7 +11386,8 @@
 
       <para>
         Part of the MySQL installation process is to set up the
-        <literal>mysql</literal> database containing the grant tables:
+        <literal>mysql</literal> database that contains the grant
+        tables:
       </para>
 
       <itemizedlist>
@@ -11434,8 +11447,8 @@
                 On Unix, both <literal>root</literal> accounts are for
                 connections from the local host. Connections must be
                 made from the local host by specifying a hostname of
-                <literal>localhost</literal> for one account, or the
-                actual hostname or IP number for the other.
+                <literal>localhost</literal> for one of the accounts, or
+                the actual hostname or IP number for the other.
               </para>
             </listitem>
 
@@ -11449,8 +11462,8 @@
         <listitem>
           <para>
             Two anonymous-user accounts are created, each with an empty
-            username. The anonymous accounts have no passwords, so
-            anyone can use them to connect to the MySQL server.
+            username. The anonymous accounts have no password, so anyone
+            can use them to connect to the MySQL server.
           </para>
 
           <itemizedlist>
@@ -11461,8 +11474,8 @@
                 from the local host. It has all privileges, just like
                 the <literal>root</literal> accounts. The other is for
                 connections from any host and has all privileges for the
-                <literal>test</literal> database or other databases with
-                names that start with <literal>test</literal>.
+                <literal>test</literal> database and for other databases
+                with names that start with <literal>test</literal>.
               </para>
             </listitem>
 
@@ -11471,11 +11484,11 @@
                 On Unix, both anonymous accounts are for connections
                 from the local host. Connections must be made from the
                 local host by specifying a hostname of
-                <literal>localhost</literal> for one account, or the
-                actual hostname or IP number for the other. These
+                <literal>localhost</literal> for one of the accounts, or
+                the actual hostname or IP number for the other. These
                 accounts have all privileges for the
-                <literal>test</literal> database or other databases with
-                names that start with <literal>test_</literal>.
+                <literal>test</literal> database and for other databases
+                with names that start with <literal>test_</literal>.
               </para>
             </listitem>
 
@@ -11495,14 +11508,15 @@
         <listitem>
           <para>
             If you want to prevent clients from connecting as anonymous
-            users without a password, you should either assign passwords
-            to the anonymous accounts or else remove them.
+            users without a password, you should either assign a
+            password to each anonymous account or else remove the
+            accounts.
           </para>
         </listitem>
 
         <listitem>
           <para>
-            You should assign passwords to the MySQL
+            You should assign a password to each MySQL
             <literal>root</literal> accounts.
           </para>
         </listitem>
@@ -11523,14 +11537,15 @@
         You might want to defer setting the passwords until later, so
         that you don't need to specify them while you perform additional
         setup or testing. However, be sure to set them before using your
-        installation for any real production work.
+        installation for production purposes.
       </para>
 
       <para>
-        To assign passwords to the anonymous accounts, you can use
-        either <literal>SET PASSWORD</literal> or
-        <literal>UPDATE</literal>. In both cases, be sure to encrypt the
-        password using the <literal>PASSWORD()</literal> function.
+        To assign passwords to the anonymous accounts, connect to the
+        server as <literal>root</literal> and then either <literal>SET
+        PASSWORD</literal> or <literal>UPDATE</literal>. In either case,
+        be sure to encrypt the password using the
+        <literal>PASSWORD()</literal> function.
       </para>
 
       <para>
@@ -11628,7 +11643,7 @@
 </programlisting>
 
       <para>
-        This account allows anonymous access but has full privileges, so
+        That account allows anonymous access but has full privileges, so
         removing it improves security.
       </para>
 
@@ -11702,8 +11717,8 @@
       </para>
 
 <programlisting>
-shell&gt; mysqladmin -u root password "<replaceable>newpwd</replaceable>"
-shell&gt; mysqladmin -u root -h <replaceable>host_name</replaceable> password "<replaceable>newpwd</replaceable>"
+shell&gt; <userinput>mysqladmin -u root password "<replaceable>newpwd</replaceable>"</userinput>
+shell&gt; <userinput>mysqladmin -u root -h <replaceable>host_name</replaceable> password "<replaceable>newpwd</replaceable>"</userinput>
 </programlisting>
 
       <para>
@@ -11743,19 +11758,20 @@
 
 <programlisting>
 shell&gt; <userinput>mysqladmin -u root -p shutdown</userinput>
-Enter password: <userinput>(enter root password here)</userinput>
+Enter password: <replaceable>(enter root password here)</replaceable>
 </programlisting>
 
       <para>
         <emphasis role="bold">Note</emphasis>: If you forget your
-        <literal>root</literal> password after setting it up, the
-        procedure for resetting it is covered in
-        <xref linkend="resetting-permissions"/>.
+        <literal>root</literal> password after setting it up,
+        <xref linkend="resetting-permissions"/>, covers the procedure
+        for resetting it.
       </para>
 
       <para>
-        To set up new accounts, you can use the <literal>GRANT</literal>
-        statement. For instructions, see <xref linkend="adding-users"/>.
+        To set up additional accounts, you can use the
+        <literal>GRANT</literal> statement. For instructions, see
+        <xref linkend="adding-users"/>.
       </para>
 
     </section>

Thread
svn commit - mysqldoc@docsrva: r1144 - in trunk: . refman-4.1 refman-5.0 refman-5.1paul31 Jan