svn commit - mysqldoc@docsrva: r15761 - trunk/dynamic-docs/changelog

[anthony.bedford]

Author: tbedford
Date: 2009-07-20 16:45:26 +0200 (Mon, 20 Jul 2009)
New Revision: 15761

Log:
An entry was added for dev bug #43701

Modified:
   trunk/dynamic-docs/changelog/monitor.xml


Modified: trunk/dynamic-docs/changelog/monitor.xml
===================================================================
--- trunk/dynamic-docs/changelog/monitor.xml	2009-07-20 14:17:17 UTC (rev 15760)
+++ trunk/dynamic-docs/changelog/monitor.xml	2009-07-20 14:45:26 UTC (rev 15761)
Changed blocks: 1, Lines Added: 71, Lines Deleted: 0; 2155 bytes

@@ -9,6 +9,77 @@
   <logentry entrytype="bug">
 
     <bugs>
+      <fixes bugid="43701"/>
+    </bugs>
+
+    <versions>
+      <version ver="2.1.0"/>
+    </versions>
+
+    <message>
+
+      <para>
+        The advisor <quote>Replication - Slave Has Login Accounts With
+        Inappropriate Privileges</quote> contained inappropriate advice
+        information.
+      </para>
+
+      <para>
+        The advice message generated was:
+      </para>
+
+<programlisting>
+Server: slave-01
+Time: 2009-03-17 12:00:04 GMT
+Advisor: Replication - Slave Has Login Accounts With Inappropriate Privileges
+
+Problem Description
+Altering and dropping tables on a slave can break replication. Unless the slave also hosts
+non-replicated tables, there is no need for accounts with these privileges.
+
+Advice
+Revoke the global ALTER and DROP privileges from the following accounts on server slave-01
+unless they are absolutely necessary:
+
+user_1@localhost,
+user_2@localhost
+
+Recommended Action
+REVOKE ALTER, DROP ON *.* FROM user_name@host_name;
+FLUSH PRIVILEGES;</programlisting>
+
+      <para>
+        However, the problems with this advice were:
+      </para>
+
+      <orderedlist>
+
+        <listitem>
+          <para>
+            The server was configured <literal>read_only</literal> so it
+            would not be possible to <literal>DROP</literal> or
+            <literal>ALTER</literal> tables unless the user had
+            <literal>SUPER</literal> privilege.
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            MySQL grants were replicated from the master and therefore
+            appeared on the slave. Also, <literal>read_only</literal>
+            ensured the slave could not be changed.
+          </para>
+        </listitem>
+
+      </orderedlist>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
       <fixes bugid="41717"/>
     </bugs>