Oracle 5.0 Reference Manual page 180

getpwnam: No such file or directory
To work around this problem, start
[424]
--user
so that
mysqld
Another solution, which solves both problems, is not to use a binary distribution. Obtain a MySQL
source distribution (in RPM or
On some Linux 2.2 versions, you may get the error
clients make a great many new connections to a
Linux has a delay between the time that you close a TCP/IP socket and the time that the system
actually frees it. There is room for only a finite number of TCP/IP slots, so you encounter the resource-
unavailable error if clients attempt too many new TCP/IP connections over a short period of time. For
example, you may see the error when you run the MySQL
We have inquired about this problem a few times on different Linux mailing lists but have never been
able to find a suitable resolution. The only known "fix" is for clients to use persistent connections,
or, if you are running the database server and clients on the same machine, to use Unix socket file
connections rather than TCP/IP connections.
2.20.1.3. Linux Source Distribution Notes
The following notes regarding
are running Linux on an x86 machine, in most cases it is much better for you to use our binary. We link
our binaries against the best patched version of
in an attempt to make it suitable for a high-load server. For a typical user, even for setups with a lot of
concurrent connections or tables exceeding the 2GB limit, our binary is the best choice in most cases.
After reading the following text, if you are in doubt about what to do, try our binary first to determine
whether it meets your needs. If you discover that it is not good enough, you may want to try your own
build. In that case, we would appreciate a note about it so that we can build a better binary next time.
MySQL uses LinuxThreads on Linux. If you are using an old Linux version that doesn't have glibc2,
you must install LinuxThreads before trying to compile MySQL. You can obtain LinuxThreads from
http://dev.mysql.com/downloads/os-linux.html.
Note that
glibc
pthread_mutex_timedwait()
issued. Do not use
Note that Linux kernel and the LinuxThread library can by default handle a maximum of 1,024 threads.
If you plan to have more than 1,000 concurrent connections, you need to make some changes to
LinuxThreads, as follows:
• Increase
and decrease
the root of glibc. (Note that MySQL is not stable with 600 to 1000 connections if
the default of 2MB.)
• Recompile LinuxThreads to produce a new
There is another issue that greatly hurts MySQL performance, especially on SMP systems. The mutex
implementation in LinuxThreads in
the mutex only for a short time. This produces a paradoxical result: If you link MySQL against an
unmodified LinuxThreads, removing processors from an SMP actually improves MySQL performance
in many cases. We have made a patch available for
dev.mysql.com/Downloads/Linux/linuxthreads-2.1-patch).
With
glibc
one in
glibc
option. This causes the system itself to change the user ID of the
need not do so.
.tar.gz
glibc
versions before and including version 2.1.1 have a fatal bug in
INSERT DELAYED
PTHREAD_THREADS_MAX
in
STACK_SIZE linuxthreads/internals.h
2.2.2, MySQL uses the adaptive mutex, which is much better than even the patched
2.1.3. Be warned, however, that under some conditions, the current mutex code in
Linux Notes
by using the
mysqld
format) and install that instead.
Resource temporarily unavailable
mysqld
apply only to the situation when you build MySQL yourself. If you
we can find and with the best compiler options,
glibc
handling, which is used when
before upgrading glibc.
in
sysdeps/unix/sysv/linux/bits/local_lim.h
libpthread.a
2.1 is very poor for programs with many threads that hold
glibc
glibc
160
command rather than by specifying the
su
server over TCP/IP. The problem is that
benchmark over TCP/IP.
test-connect
INSERT DELAYED
to 256KB. The paths are relative to
library, and relink MySQL against it.
2.1.3 to correct this behavior
process
mysqld
when
statements are
to 4096
is
STACK_SIZE
(http://