bk commit - mysqldoc tree (1.448)

Below is the list of changes that have just been committed into a local
mysqldoc repository of lenz. When lenz 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.448 03/04/24 21:08:53 lenz@xxxxxxxxx +1 -0
   - Updated FreeBSD info

  Docs/manual.texi
    1.422 03/04/24 21:08:52 lenz@xxxxxxxxx +18 -2
     - Updated FreeBSD info

# 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: lenz
# Host: kallisto.local
# Root: /space/my/mysqldoc

--- 1.421/Docs/manual.texi      Thu Apr 24 16:54:27 2003
+++ 1.422/Docs/manual.texi      Thu Apr 24 21:08:52 2003
@@ -6384,6 +6384,8 @@
 @item
 FreeBSD 3.x and 4.x with native threads.  @xref{FreeBSD}.
 @item
+FreeBSD 4.x with Linuxthreads.  @xref{FreeBSD}.
+@item
 HP-UX 10.20 with the DCE threads or the MIT-pthreads package.
 @xref{HP-UX 10.20}.
 @item
@@ -11178,7 +11180,7 @@
 @node FreeBSD, NetBSD, BSD Notes, BSD Notes
 @subsubsection FreeBSD Notes
 
-FreeBSD 3.x is recommended for running MySQL since the thread package
+FreeBSD 4.x is recommended for running MySQL since the thread package
 is much more integrated.
 
 The easiest and therefore the preferred way to install is to use the
@@ -11204,8 +11206,22 @@
 @end itemize
 
 It is recommended you use MIT-pthreads on FreeBSD 2.x and native threads on
-Versions 3 and up. It is possible to run with  native threads on some late
+Versions 3 and up. It is possible to run with native threads on some late
 2.2.x versions but you may encounter problems shutting down @code{mysqld}.
+
+Unfortunately, certain function calls on FreeBSD are not yet fully
+thread-safe, most notably the @code{gethostbyname()} function, which is
+used by MySQL to convert host names into IP addresses. Under certain
+circumstances, the @code{mysqld} process will suddenly cause 100%
+CPU load and will be unresponsive. If you encounter this, try to start
+up MySQL using the @code{--skip-name-resolve} option.
+
+Alternatively, you can link MySQL on FreeBSD 4.x against the LinuxThreads
+library, which avoids a few of the problems that the native FreeBSD thread
+implementation has. For a very good comparison of LinuxThreads vs. native
+threads have a look at Jeremy Zawodny's article "FreeBSD or Linux for your
+MySQL Server?" at
+@uref{http://jeremy.zawodny.com/blog/archives/000203.html}.
 
 The MySQL @file{Makefile}s require GNU make (@code{gmake}) to work.  If
 you want to compile MySQL you need to install GNU @code{make} first.

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