I'm running OpenBSD 2.8 and MySQL 3.22.32 (recent cvs port).
After time ( 1day) the cpu load for the mysqld process goes up to 98%..
There is a known problem in 2.8 thread library. I do not know
when will they fix it. You can ask them , though ..
I've seen that this has been addressed in the
Doing a "make" on the newest MySQL stable 3.23.36 source tarball - on a
stock Cobalt RaQ3 (Linux 386) which I've installed MySQL on many times before.
Got this strange error:
gcc -DUNDEF_THREADS_HACK -DHAVE_CONFIG_H -I./../include -I./.. -I..-O6
-DDBUG_OFF -c readline.c
In file
Running the standard (brand-new) OpenBSD install of MySQL from
/usr/ports/databases/mysql/
Version 3.23.32 - the port that Brad made just a few days ago. No
options. Just "make install".
It works fine exceptI keep getting this error:
ERROR 2006: MySQL server has gone away
It comes back
"fieldname=" - then end it with "@END@"
--
Derek Sivers, CD Baby
[EMAIL PROTECTED] (503)595-3000
www.cdbaby.com | www.cdbaby.net
-
Before posting, please check:
http://www.mysql.com/manual.php (the man
y email, not to the whole list.
Thanks!
--
Derek Sivers
[EMAIL PROTECTED]
-
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this t
At 09:58 PM 1/23/01 , Manuel Leos wrote:
Hi everybody, I'm trying to install the RPM on a RH
7.0 everything looks normal but the server dies
sending this message
mysqld: Can't find file: 'host.ISM' (errno: 2)
It's part of the first database/table that MySQL sets up for you.
I get this error
Don't use RPM.
The RPMs for the Cobalt RaQ3 suck.
I have 8 different Cobalt RaQ3's and here's the way I've used to install:
I've installed it this way successfully each time.
Sounds like a bit of a pain, but puts you in much better control of MySQL.
INSTALLATION INSTRUCTIONS
#1 -
Has anyone done testing to show the difference between:
#1 - having MySQL on the same server as Apache/PHP
vs.
#2 - having MySQL on its own dedicated computer, TCP/IP connected to the
main Apache box
NOTE: We use lots of little MySQL lookups in our PHP scripts. Nothing
that intensive.