bk commit - mysqldoc tree (jon:1.2804)

[jon]

Below is the list of changes that have just been committed into a local
mysqldoc repository of jon. When jon does a push these changes will
be propagated to the main repository and, within 24 hours after the
push, to the public repository.
For information on how to access the public repository
see http://www.mysql.com/doc/I/n/Installing_source_tree.html

ChangeSet
  1.2804 05/04/03 14:54:58 jon@stripped +1 -0
  Cluster: corrected/clarified what the diskless option 
  does with regard to ndbd process. 

  Docs/manual.texi
    1.2637 05/04/03 14:54:54 jon@stripped +4 -3
    Cluster: corrected/clarified what the diskless option 
    does with regard to ndbd process. 

# This is a BitKeeper patch.  What follows are the unified diffs for the
# set of deltas contained in the patch.  The rest of the patch, the part
# that BitKeeper cares about, is below these diffs.
# User:	jon
# Host:	gigan.site
# Root:	/home/jon/bk/mysqldoc

--- 1.2636/Docs/manual.texi	2005-04-03 14:48:03 +10:00
+++ 1.2637/Docs/manual.texi	2005-04-03 14:54:54 +10:00
@@ -73372,9 +73372,10 @@
 @item [NDBD]Diskless
 It is possible to specify Cluster tables as @strong{diskless}, meaning that
 tables are not checkpointed to disk and that no logging occurs. Such tables
-exist only in main memory. A consequence of using diskless tables is that the
-tables will still be defined after a crash, but records in those tables will
-not be preserved.
+exist only in main memory. A consequence of using diskless tables is that
+neither the tables nor the records in those tables will be preserved after a
+crash. However, when operating in diskless mode, it is possible to run
+@command{ndbd} on a diskless computer.
 
 This feature makes the entire cluster operate in diskless mode. We plan to add
 the capability to employ diskless mode on a per-table basis in a future