Home  >  Article  >  Database  >  Getting MySql Up and Running after Upgrading to Mavericks_MySQL

Getting MySql Up and Running after Upgrading to Mavericks_MySQL

WBOY
WBOYOriginal
2016-06-01 13:16:28920browse

I recently upgraded my Mac to Mavericks and, of course, MySql was hosed afterwards. I use MySql a lot for development and demos and dreaded going through the pain of getting it running again. I recalled the initial installation was fairly unpleasant, with a bit of trial and error before I finally had my test databases the way I wanted them. When I upgraded to Mavericks, I panicked when my tests started failing with errors connecting to MySql. Alas, it was broken. A bit of Googling indicated that it needed to be reinstalled on Mavericks, which was not actually true. Had I seenthisfirst, I would have known better.Anyway, I came across thisApple User Tipthat not only made installation and setup a snap, but made integration with OSx even better. Here is a summary from the article:

1.Download MySQL, if you haven't already. The article indicates to download the OSx 10.6 pkg with the dmg. I wanted the latest, so I got mysql-5.6.17-osx10.7-x86_64.tar.gz and extracted to/usr/local/mysql. Either way seems fine though.

2. Runsudo vi /Library/LaunchDaemons/com.mysql.mysql.plist, add and save the following:

 

    KeepAlive

   

    Label

    com.mysql.mysqld

    ProgramArguments

   

    /usr/local/mysql/bin/mysqld_safe

    --user=mysql

   

 

3. Runsudo vi /etc/my.cnf, add and save the following:

[client]

socket=/var/mysql/mysql.sock

[mysqld]

socket=/var/mysql/mysql.sock

4. Runsudo launchctl load -w /Library/LaunchDaemons/com.mysql.mysql.plistand MySql will start. You are then ready toset the root password and add any users.

Hopefully this will save you some time. There are lots of things like this that can be a pain to do (or remember what you did last time). As I come across those, I will add them here.

Statement:
The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn