[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: MySQL Connections on the Alpha
- From: Maurice Hilarius <maurice harddata com>
- To: axp-list redhat com
- Subject: Re: MySQL Connections on the Alpha
- Date: Sun, 29 Nov 1998 12:12:13 -0700
With regards to your message at 03:47 AM 11-29-98 -0500, Mark Conway Wirt.
Where you stated:
>
>I know I've seem post on the list where people have gotten MySQL to
>work on the Alpha, but I'm, unfortunately, not one of them. Can't
>find anything to help me in the archive (redhat's search is broken
>once again and alphalinux.org doesn't have much of an archive yet...)
>
>I've tried using the precompiled binaries, and could never get the
>thing to pass the tests. Tonight I decided to recompile from scratch
>using MySQL 3.21.32a with an up-to-date RH 5.2, and I have the same
>problem.
>
>The code compiles fine (well, I had to tweak it a bit -- like turning
>off optimization and playing with the includes), and runs to an
>extent. It will pass all of the tests, with the exception of the
>connect test. The test will connect/disconnect with the database
>fine, but I get a memory violation in the next part of the test.
>
>Is *anyone* out there running MySQL to an extent that it passes the
>sql-bench tests, or is it just me?
>
>--Mark
Hi Mark. A good starting place to read is at:
http://www.tcx.se/Manual_chapter/manual_Installing.html#Which_OS
Look about 1/3 down for Alpha Linux notes. Usually there is a small problem
with Linuxthreads:
"The first problem is LinuxThreads. The RedHat distribution uses an old
(broken) LinuxThreads version, so you must patch LinuxThreads for Alpha.
Use the following
procedure:
<<<<snip>>
If you have problems with signals (MySQL dies unexpectedly under high load)
you may have found an OS bug with threads and signals. In this case you can
tell MySQL
not to use signals by configuring with:
shell> CFLAGS=-DDONT_USE_THR_ALARM CXXFLAGS=-DDONT_USE_THR_ALARM
./configure ...
This doesn't affect the performance of MySQL, but has the side effect that
you can't kill clients that are "sleeping" on a connection with mysqladmin
kill or mysqladmin
shutdown. The client will instead die when it issues its next command. "
Best regards,
Maurice W. Hilarius Telephone: 01-403-414-9319
Hard Data Ltd. **FAX: 01-403-456-1510
11060 - 166 Avenue email:maurice@harddata.com
Edmonton, AB, Canada - T5X 1Y3 http://www.harddata.com
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
[]