bk commit - mysqldoc tree (1.456)

Below is the list of changes that have just been committed into a local
mysqldoc repository of guilhem. When guilhem 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.456 03/04/27 23:46:39 guilhem@xxxxxxxxx +1 -0
  Tell users to look into their .err or SHOW SLAVE STATUS
  after START SLAVE, because START SLAVE won't tell them that
  slave threads stopped after start.

  Docs/manual.texi
    1.430 03/04/27 23:46:37 guilhem@xxxxxxxxx +10 -1
    Tell users to look into their .err or SHOW SLAVE STATUS
    after START SLAVE, because START SLAVE won't tell them that
    slave threads stopped after start.

# 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: guilhem
# Host: gbichot.local
# Root: /home/mysql_src/mysqldoc

--- 1.429/Docs/manual.texi      Sun Apr 27 21:03:28 2003
+++ 1.430/Docs/manual.texi      Sun Apr 27 23:46:37 2003
@@ -26405,7 +26405,16 @@
 As of MySQL 4.0.2, you can add @code{IO_THREAD} or @code{SQL_THREAD}
 options to the statement to start only 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.
+relay log.  The SQL thread reads the relay log and executes the
+queries.
+Note that if @code{START SLAVE} succeeds in starting the slave threads it
+will return without any error. But even in that case it might be that slave
+threads start and then later stop (because they don't manage to
+connect to the master or read his binlogs or any other
+problem). @code{START SLAVE} will not warn you about this, you have to
+check your slave's @file{.err} file for error messages generated by
+the slave threads, or check that these are running fine with @code{SHOW
+SLAVE STATUS}.
 
 @node STOP SLAVE
 @subsubsection @code{STOP SLAVE} (slave)

-- 
MySQL Internals Mailing List
For list archives: http://lists.mysql.com/internals
To unsubscribe:    
http://lists.mysql.com/internals?unsub=gcdmd-internals@xxxxxxxxxxx