I'm not sure if anyone cares but... here's my final post on this topic.
I believe my signal 11 problem was due to me installing the 3.23.34 rpms
from mysql.com on top of my Redhat 7.0 system. I had heard that the RPMs
on mysql.com are Redhat 6.2 based and thus may be expecting different
dynamic libraries (libc?).
Normally, rpms will complain about missing dependencies, but it's possible
the ones on mysql.com were not made to check such things.
I'm not really sure this is the problem, but it's a good enough guess that
I'm willing to let it go now.
I've installed the 3.23.32 rpms for 7.0 from redhat.com and it went
smoothly. So far no signal 11's.
Interestingly, redhat has got a different (and I think more standard)
mysqld start script (for /etc/init.d/rc.d/mysqld - note the name change
from ".../rc.d/mysql"). I had to edit it though as it had a --default
option for safe_mysqld that mysqld had never heard of (odd).
From now on, I'll be restricting myself to redhat.com's 7.0 Mysql rpms. I
can live with being a few releases behind (sounds like the mysql people
recommend not installing new release right away anyway).
over and out,
-bill
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
