svn commit - mysqldoc@docsrva: r3014 - in trunk: refman-4.1 refman-5.0 refman-5.1

[jon]

Author: jstephens
Date: 2006-08-15 05:25:23 +0200 (Tue, 15 Aug 2006)
New Revision: 3014

Log:
Cluster log not *always* in DataDir (Thanks, Roland!)

Modified:
   trunk/refman-4.1/mysql-cluster.xml
   trunk/refman-5.0/mysql-cluster.xml
   trunk/refman-5.1/mysql-cluster.xml


Modified: trunk/refman-4.1/mysql-cluster.xml
===================================================================
--- trunk/refman-4.1/mysql-cluster.xml	2006-08-14 19:59:25 UTC (rev 3013)
+++ trunk/refman-4.1/mysql-cluster.xml	2006-08-15 03:25:23 UTC (rev 3014)
Changed blocks: 1, Lines Added: 8, Lines Deleted: 5; 1466 bytes

@@ -9777,11 +9777,14 @@
       checked, log levels changed, backups started and stopped, and
       nodes stopped and started. The second method involves studying the
       contents of the cluster log
-     
<filename>ndb_<replaceable>node_id</replaceable>_cluster.log</filename>
-      in the management server's <literal>DataDir</literal> directory.
-      (Recall that <replaceable>node_id</replaceable> represents the
-      unique identifier of the node whose activity is being logged.) The
-      cluster log contains event reports generated by
+     
<filename>ndb_<replaceable>node_id</replaceable>_cluster.log</filename>;
+      this is usually found in the management server's
+      <literal>DataDir</literal> directory, but this location can be
+      overridden using the <literal>LogDestination</literal> option
+      &mdash; see <xref linkend="mysql-cluster-mgm-definition"/>, for
+      details. (Recall that <replaceable>node_id</replaceable> 
+      represents the unique identifier of the node whose activity is
+      being logged.) The cluster log contains event reports generated by
       <command>ndbd</command>. It is also possible to send cluster log
       entries to a Unix system log.
     </para>


Modified: trunk/refman-5.0/mysql-cluster.xml
===================================================================
--- trunk/refman-5.0/mysql-cluster.xml	2006-08-14 19:59:25 UTC (rev 3013)
+++ trunk/refman-5.0/mysql-cluster.xml	2006-08-15 03:25:23 UTC (rev 3014)
Changed blocks: 1, Lines Added: 8, Lines Deleted: 5; 1466 bytes

@@ -9819,11 +9819,14 @@
       checked, log levels changed, backups started and stopped, and
       nodes stopped and started. The second method involves studying the
       contents of the cluster log
-     
<filename>ndb_<replaceable>node_id</replaceable>_cluster.log</filename>
-      in the management server's <literal>DataDir</literal> directory.
-      (Recall that <replaceable>node_id</replaceable> represents the
-      unique identifier of the node whose activity is being logged.) The
-      cluster log contains event reports generated by
+     
<filename>ndb_<replaceable>node_id</replaceable>_cluster.log</filename>;
+      this is usually found in the management server's
+      <literal>DataDir</literal> directory, but this location can be
+      overridden using the <literal>LogDestination</literal> option
+      &mdash; see <xref linkend="mysql-cluster-mgm-definition"/>, for
+      details. (Recall that <replaceable>node_id</replaceable> 
+      represents the unique identifier of the node whose activity is
+      being logged.) The cluster log contains event reports generated by
       <command>ndbd</command>. It is also possible to send cluster log
       entries to a Unix system log.
     </para>


Modified: trunk/refman-5.1/mysql-cluster.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster.xml	2006-08-14 19:59:25 UTC (rev 3013)
+++ trunk/refman-5.1/mysql-cluster.xml	2006-08-15 03:25:23 UTC (rev 3014)
Changed blocks: 1, Lines Added: 8, Lines Deleted: 5; 1466 bytes

@@ -9702,11 +9702,14 @@
       checked, log levels changed, backups started and stopped, and
       nodes stopped and started. The second method involves studying the
       contents of the cluster log
-     
<filename>ndb_<replaceable>node_id</replaceable>_cluster.log</filename>
-      in the management server's <literal>DataDir</literal> directory.
-      (Recall that <replaceable>node_id</replaceable> represents the
-      unique identifier of the node whose activity is being logged.) The
-      cluster log contains event reports generated by
+     
<filename>ndb_<replaceable>node_id</replaceable>_cluster.log</filename>;
+      this is usually found in the management server's
+      <literal>DataDir</literal> directory, but this location can be
+      overridden using the <literal>LogDestination</literal> option
+      &mdash; see <xref linkend="mysql-cluster-mgm-definition"/>, for
+      details. (Recall that <replaceable>node_id</replaceable> 
+      represents the unique identifier of the node whose activity is
+      being logged.) The cluster log contains event reports generated by
       <command>ndbd</command>. It is also possible to send cluster log
       entries to a Unix system log.
     </para>