bk commit into 4.0 tree

[paul]

Below is the list of changes that have just been committed into a local
4.0 repository of paul. When paul 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@stripped, 2002-10-07 09:53:17-05:00, paul@stripped
  manual.texi	Document IO_THREAD and SQL_THREAD for SLAVE START/STOP.

  Docs/manual.texi
    1.1217 02/10/07 09:49:54 paul@stripped +8 -2
    Document IO_THREAD and SQL_THREAD for SLAVE START/STOP.

# 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:	paul
# Host:	teton.kitebird.com
# Root:	/home/paul/mysql-4.0

--- 1.1216/Docs/manual.texi	Mon Oct  7 06:28:50 2002
+++ 1.1217/Docs/manual.texi	Mon Oct  7 09:49:54 2002
@@ -24321,10 +24321,16 @@
 @item @strong{Command} @tab @strong{Description}
 
 @item @code{SLAVE START}
- @tab Starts the slave thread. (Slave)
+ @tab Starts the slave thread.
+As of MySQL 4.0.2, you can add @code{IO_THREAD} or @code{SQL_THREAD}
+options to the statement to start the I/O thread or the SQL thread.
+The I/O thread reads queries from the master server and stores them in the
+relay log.  The SQL thread reads the relay log and executes the queries.
+(Slave)
 
 @item @code{SLAVE STOP}
- @tab Stops the slave thread. (Slave)
+ @tab Stops the slave thread. Like @code{SLAVE START}, this statement
+may be used with @code{IO_THREAD} and @code{SQL_THREAD} options. (Slave)
 
 @item @code{SET SQL_LOG_BIN=0}
 @tab Disables update logging if the user has the @code{SUPER} privilege.