So this will show you: $ ps -axjc | grep mysql From the Terminal run a ps command to find out what the process is you can use -j or -l to list out the parent id ppid.
Start off by finding out what the parent process is that started your mysql.
Note: you may also have the MySQL Preference Pane installed at /Library/PreferencePanes/MySQL.prefpane or ~/Library/PreferencePanes/ preference pane can also be removed to 'cleanup' pieces of the old MySQL installation. 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 You can terminate the currently running instance of mysqld by performing the command: sudo /Library/StartupItems/MYSQLCOM/MYSQLCOM stop 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). If so, the startup script will launch mysqld. 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-". The startup script that's launching the conflicting version of MySQL is most likely located at /Library/StartupItems/MYSQLCOM/MYSQLCOM. In fact, even the current binary distribution (5.6.15) of mysqld uses StartupItems to start the server on OS X(?!) For some reason, the startup script that is distributed with MySQL uses the deprecated "Startup items" technology to start processes at boot. 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.
0 kommentar(er)
