Several people have notified me of the problem they discovered when checking the version that is installed after they manually compiled MySQL from source after the binary install. The mysqld located in ‘/usr/local/mysql/bin‘ directory keeps reflecting the original installed version and not the latest source compiled version.
It took me a while to find out what was wrong here but I solved it. It is my mistake as I did not discover this earlier. The mysqld program when compiling from source is located in ‘/usr/local/mysql/libexec‘ and is properly referenced is you use the ‘mysqld_safe‘ program to start it up. The mysqld binary in ‘/usr/local/mysql/bin‘ is a left-over of the binary install procedure and is no longer used or referenced. This also means that my startup script was incorrect.
As a consequence I’ve changed the startup plist file. Please do the same by first changing the plist file and then do:
sudo launchctl load /System/Library/LaunchDaemons/com.diymacserver.mysql.plist
Then the newer version should be running. You can check this by using the command:
Thanks to the vigilant users and my apologies to the others.
Comments
9:03 pm
Richard,
For the Leopard install, I have tried to find the startup command for MySQL. Yet, from many different place on the internet, I have not found out the correct command to do so. This is a critical step that I think you should include in all of your documentation for every version that you have listed here. As a result, I cannot follow the step to secure the MySQL install. Heck, I cannot even start it to see if it worked correctly after a 2 hour long make then hour long make install. Once again, thank you for your time and your consideration.
Quicksilver G4 867Mhz
1.25 MB Ram
Client OS-X 10.5.8
Dante’
7:49 pm
@Dante, did you find this page in the Leopard documentation? http://diymacserver.com/installing-mysql/starting-mysql-on-leopard/
Basically the startup command for mysql on any platform is mysqld_safe