Got it. mysqladmin version showed the 4.0.4 version.
The Find is what clued me in. It did indeed find two mysqld executables. One in /usr/local/share/mysql/... and the other in /usr/local/mysql/share/mysql/...
I copied the right one over the wrong one and after cleaning up a couple of error messages, it came up fine. I'm wondering about how that happened. Do those two versions default to installing in two different places, or did I somehow do that by mistake?
Hard to say. In your original message, you indicated that you compiled the 4.0.16 distribution yourself, but didn't specify whether you also compiled 4.0.4 yourself. If you did, then you probably used slightly different configuration options to build the two distributions. At least, that would account for the phenomenon you observed.
If you compiled 4.0.16, but installed 4.0.4 from an RPM file, that might also account for it. RPMs use a layout that can be discovered using rpm -qpl on the RPM file.
I'm curious now as to what we'll have to watch out for now having two installs in two different places now. Is cleaning it up as easy as putting the databases in the right directory, then rm -rf the bad one?
Depends. If you installed 4.0.4 from an RPM, you can use rpm to erase it. If there is no overlap between the 4.0.4 and 4.0.16 installation, this should leave your 4.0.16 installation untouched. Of course, it's difficult to say whether this is true. If there is overlap, removing the old installation will remove part of your new installation. (In which case, you might want to re-install 4.0.16 after removing 4.0.4.)
Make sure you generate a backup of your databases first, whatever you do.
Thanks again! Mark
-- Paul DuBois, Senior Technical Writer Madison, Wisconsin, USA MySQL AB, www.mysql.com
Are you MySQL certified? http://www.mysql.com/certification/
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
