From 596c3fc5498236df732d0e5e14e769ee7eb83d1c Mon Sep 17 00:00:00 2001
From: "paul@teton.kitebird.com" <>
Date: Sun, 4 Aug 2002 22:39:53 -0500
Subject: [PATCH] manual.texi	restrict scope of a mysql.server comment

---
 Docs/manual.texi | 10 ++++++----
 1 file changed, 6 insertions(+), 4 deletions(-)

diff --git a/Docs/manual.texi b/Docs/manual.texi
index dd2032e0a94..bd9b34936c3 100644
--- a/Docs/manual.texi
+++ b/Docs/manual.texi
@@ -23164,10 +23164,12 @@ to the log file (by default named @file{'hostname'.log}).  This log can
 be very useful when you suspect an error in a client and want to know
 exactly what @code{mysqld} thought the client sent to it.
 
-By default, the @code{mysql.server} script starts the MySQL
-server with the @code{-l} option.  If you need better performance when
-you start using MySQL in a production environment, you can
-remove the @code{-l} option from @code{mysql.server} or change it to
+@c Note: this instance of "safe_mysql" should not be changed to "mysqld_safe"
+@c because it's a 3.23.x-specific command
+Older versions of the @code{mysql.server} script (from MySQL 3.23.4 to 3.23.8)
+pass @code{safe_mysqld} a @code{--log} option.  If you need better performance
+when you start using MySQL in a production environment, you can remove the
+@code{--log} option from @code{mysql.server} or change it to
 @code{--log-bin}.
 
 The entries in this log are written as @code{mysqld} receives the questions.