This is not a secure option for a production server, but should suffice for hobbyists running MySQL on a local machine.Fill in the fields like this, making sure that you use ‘localHost’ as the URL, and make sure you check the Disable button for this step. It will run at login (NOT startup - there is a difference) and get MySQL going. Set this application as a Login Item by clicking on the Accounts icon of System Preferences. Be sure to check the "Run Only" checkbox (to protect your password from prying eyes) and do not check the "Startup Screen" and "Stay Open" checkbox. Insert your password in the correct spot and save as an application. Set cli to "sudo /usr/local/mysql/bin/mysqld_safe &> /dev/null &"set pswd to "mypassword"sudoshell(cli, pswd)on sudoshell(cli, pswd) - display dialog cli do shell script cli password pswd with administrator privilegesend sudoshell Step 2 - To fix the startup issue, execute this line in the Terminal (you will need admin permissions): sudo chown -R root:wheel /Library/StartupItems/MySQLCOMFor example: jwb% sudo chown -R root:wheel /Library/StartupItems/MySQLCOMWell that was easy!Īn alternative solution is to use the following Applescript. Mysqld_pid_file_path=$datadir/`/bin/hostname`.pid # mysqld_pid_file_path=$datadir/`hostname`.pid Mysqld_pid_file_path=$datadir/` /bin/hostname`.pid * ) mysqld_pid_file_path="$datadir/$mysqld_pid_file_path" Mysqld_pid_file_path=$datadir/`hostname`.pid You may view the few changes in partial context in the following table. You may view the few changes needed in living color and in full context in this PDF file. Sudo pico /usr/local/mysql/support-files/rverFor example: jwb% sudo pico /usr/local/mysql/support-files/rver To open with pico, type this at your Terminal prompt: This can be opened with pico, nano, vi, TextWrangler or whichever text editor you prefer. Step 1 - fix the file at /usr/local/mysql/support-files/rver. Hopefully I have taken this a step further and made it more clear. My thanks to the authors on these sites who provided the answer. It really seems inexcusable, and although the good folks at MySQL (I guess it's managed by Oracle now) have known about this for more than 6 months and the severity level has been raised to severe, it remains unfixed as of January 21, 2011. When/where/why it was introduced is an absolute mystery to me. The bug did not exist in version 5.1.30 of MySQL. This bug may have been fixed since this posting (maybe even before), or a new bug may have been introduced, so your mileage may vary. Since the bug is the fault of MySQL and not Apple, I expect it will work anywhere it is needed. This fix has been shown to correct issues on MacOS X 10.6.5 Server and 10.6.6 Client. As of this writing the Generally Available MySQL Community Server is at version 5.5.8, and I used the 64 bit, DMG archive. The bug occurs with the standard download from. In addition, an annoying message about incorrect permissions occurs at startup. Specifically, the PreferencePane does not actually allow startup and shutdown of the MySQL server process, and the Automatically Start MySQL Server on Startup checkbox does not work either. In fairness, the bug appears to be 100% the fault of MySQL, not Apple. Fixing the startup and PrefPane bugs with MySQL on Mac OS X 10.6 Snow LeopardThere is a bug with MySQL on Snow Leopard.
0 Comments
Leave a Reply. |