Author: mhillyer
Date: 2006-05-02 22:44:00 +0200 (Tue, 02 May 2006)
New Revision: 1993
Log:
Fix documentation bugs assigned to me.
Modified:
trunk/refman-4.1/replication.xml
trunk/refman-5.0/database-administration.xml
trunk/refman-5.0/replication.xml
trunk/refman-5.1/database-administration.xml
trunk/refman-5.1/replication.xml
Modified: trunk/refman-4.1/replication.xml
===================================================================
--- trunk/refman-4.1/replication.xml 2006-05-02 19:22:47 UTC (rev 1992)
+++ trunk/refman-4.1/replication.xml 2006-05-02 20:44:00 UTC (rev 1993)
@@ -4865,6 +4865,16 @@
</itemizedlist>
<para>
+ <emphasis role="bold">Q</emphasis>: How do I prevent GRANT and
+ REVOKE statements from replicating to slave machines?
+ </para>
+
+ <para>
+ <emphasis role="bold">A</emphasis>: Start the server with the
+ <option>--replicate-wild-ignore-table=mysql.%</option> option.
+ </para>
+
+ <para>
<emphasis role="bold">Q</emphasis>: Does replication work on mixed
operating systems (for example, the master runs on Linux while
slaves run on Mac OS X and Windows)?
Modified: trunk/refman-5.0/database-administration.xml
===================================================================
--- trunk/refman-5.0/database-administration.xml 2006-05-02 19:22:47 UTC (rev 1992)
+++ trunk/refman-5.0/database-administration.xml 2006-05-02 20:44:00 UTC (rev 1993)
@@ -12886,12 +12886,19 @@
<para>
The interval in seconds for monitoring instances. The
default value is 20 seconds. Instance Manager tries to
- connect to each monitored instance to check whether it is
- alive/not hanging. In the case of a failure, IM performs
- several attempts to restart the instance. The
- <literal>nonguarded</literal> option in the appropriate
- instance section disables this behavior for a particular
- instance.
+ connect to each monitored instance using the non-existing
+ <literal>MySQL_Instance_Manager</literal> user account to
+ check whether it is alive/not hanging. In the case of a
+ failure to connect, IM performs several attempts to
+ restart the instance. The <literal>nonguarded</literal>
+ option in the appropriate instance section disables this
+ behavior for a particular instance. The monitoring process
+ will produce messages in the general query log similar to
+ the following:
+
+<programlisting>
+Access denied for user 'MySQL_Instance_M'@'localhost' (using password: YES)
+</programlisting>
</para>
</listitem>
Modified: trunk/refman-5.0/replication.xml
===================================================================
--- trunk/refman-5.0/replication.xml 2006-05-02 19:22:47 UTC (rev 1992)
+++ trunk/refman-5.0/replication.xml 2006-05-02 20:44:00 UTC (rev 1993)
@@ -4763,6 +4763,16 @@
</itemizedlist>
<para>
+ <emphasis role="bold">Q</emphasis>: How do I prevent GRANT and
+ REVOKE statements from replicating to slave machines?
+ </para>
+
+ <para>
+ <emphasis role="bold">A</emphasis>: Start the server with the
+ <option>--replicate-wild-ignore-table=mysql.%</option> option.
+ </para>
+
+ <para>
<emphasis role="bold">Q</emphasis>: Does replication work on mixed
operating systems (for example, the master runs on Linux while
slaves run on Mac OS X and Windows)?
Modified: trunk/refman-5.1/database-administration.xml
===================================================================
--- trunk/refman-5.1/database-administration.xml 2006-05-02 19:22:47 UTC (rev 1992)
+++ trunk/refman-5.1/database-administration.xml 2006-05-02 20:44:00 UTC (rev 1993)
@@ -12948,12 +12948,19 @@
<para>
The interval in seconds for monitoring instances. The
default value is 20 seconds. Instance Manager tries to
- connect to each monitored instance to check whether it is
- alive/not hanging. In the case of a failure, IM performs
- several attempts to restart the instance. The
- <literal>nonguarded</literal> option in the appropriate
- instance section disables this behavior for a particular
- instance.
+ connect to each monitored instance using the non-existing
+ <literal>MySQL_Instance_Manager</literal> user account to
+ check whether it is alive/not hanging. In the case of a
+ failure to connect, IM performs several attempts to
+ restart the instance. The <literal>nonguarded</literal>
+ option in the appropriate instance section disables this
+ behavior for a particular instance. The monitoring process
+ will produce messages in the general query log similar to
+ the following:
+
+<programlisting>
+Access denied for user 'MySQL_Instance_M'@'localhost' (using password: YES)
+</programlisting>
</para>
</listitem>
Modified: trunk/refman-5.1/replication.xml
===================================================================
--- trunk/refman-5.1/replication.xml 2006-05-02 19:22:47 UTC (rev 1992)
+++ trunk/refman-5.1/replication.xml 2006-05-02 20:44:00 UTC (rev 1993)
@@ -5041,6 +5041,16 @@
</para>
<para>
+ <emphasis role="bold">Q</emphasis>: How do I prevent GRANT and
+ REVOKE statements from replicating to slave machines?
+ </para>
+
+ <para>
+ <emphasis role="bold">A</emphasis>: Start the server with the
+ <option>--replicate-wild-ingore-table=mysql.%</option> option.
+ </para>
+
+ <para>
<emphasis role="bold">Q</emphasis>: Does replication work on mixed
operating systems (for example, the master runs on Linux while
slaves run on Mac OS X and Windows)?
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r1993 - in trunk: refman-4.1 refman-5.0 refman-5.1 | mhillyer | 2 May |
