If the version of MySQL that was previously installed originated from the MySQL Community Downloads page on the SUN/Oracle site, it's likely that launchd
is not involved with startup of the mysqld
process. For some reason, the startup script that is distributed with MySQL uses the deprecated "Startup items" technology to start processes at boot. In fact, even the current binary distribution (5.6.15) of mysqld
uses StartupItems to start the server on OS X(?!)
The startup script that's launching the conflicting version of MySQL is most likely located at /Library/StartupItems/MYSQLCOM/MYSQLCOM
. At boot time, that startup item will examine the file at /etc/hostconfig
to determine if the setting for the "MYSQLCOM" variable is set to "-YES-". If so, the startup script will launch mysqld
.
It should be possible to disable the startup of MySQL by modifying the line in /etc/hostconfig
that specifies MYSQLCOM=-YES-
to say MYSQLCOM=-NO-
(which should disable the startup process on the next boot).
You can terminate the currently running instance of mysqld
by performing the command:
sudo /Library/StartupItems/MYSQLCOM/MYSQLCOM stop
To permanently disable the startup of the wrong mysqld
process, it should be possible to first stop the daemon using the command above, and then to remove the MySQL startup item using the following command:
sudo rm -rf /Library/StartupItems/MYSQLCOM
Note: you may also have the MySQL Preference Pane installed at /Library/PreferencePanes/MySQL.prefpane
or ~/Library/PreferencePanes/MySQL.prefpane
...That preference pane can also be removed to 'cleanup' pieces of the old MySQL installation.
ps
to track the parent process and see what is startingmysqld
?