This entry was posted in Apple, Digital Hygiene, OS X, OS X Server and tagged mavericks, mysql, os x server by Randall Rodrigues. I hope this guide helps anyone out who would like to have their homebrew mysql run as a daemon on OS X Mavericks. Sudo launchctl unload -w /Library/LaunchDaemons/ If you make changes to the plist file and need to reload it with launchctl, make sure you first unload the file: It should also now load each time the system boots. Mysqld should load immediately after this last command is run. Sudo launchctl load -w /Library/LaunchDaemons/ The last step is to load the plist with launchctl: Set the appropriate permission by changing the file mode to 644: Sudo chown root:wheel /Library/LaunchDaemons/ If it isn’t already, change the owner to root and the group to wheel. Once you have all the changes made to the plist file, you’ll want to change ownership and permissions of the file so that it will work with the launchctl process. Here is the contents of the complete plist file with all the necessary modifications: Make sure the path for your WorkingDirectory leads to folder where your mysql data is located in my case this was /usr/local/var/mysql : Where mysqlusergoeshere is the unix name of the account you want to run the mysql process. To add the user account that you would like to have run the mysqld process, add the following line under the ProgramArguments line: Then open your favorite unix text editor (vim in my case): Sudo cp /usr/local/opt/mysql/ /Library/LaunchDaemons/ You need to provide the complete path to the WorkingDirectory which on my system is /usr/local/var/mysqlīefore getting started with any changes to the included plist file, make a copy in the /Library/LaunchDaemons/ folder:.You need to provide the user account that you would like to have run the mysqld process.You’ll want to call the mysqld executable directly instead of invoking the mysqld_safe script.There are a couple of issues that need to be addressed with the default plist file if you want to run mysql as a daemon. Here is the contents of the included plist file: This can easily be accomplished by copying the file that is provided with the homebrew mysql package to the /Library/LaunchDaemons/ folder and then making some edits to the file in it’s new location. Remember, I want to have mysql run as a daemon even when there is no user actively logged into the dev server… Or, if you don't want/need launchctl, you can just run: Ln -sfv /usr/local/opt/mysql/*.plist ~/Library/LaunchAgents This is the last part of the output of the above command: You can access the info with the following command: The homebrew mysql package comes with some info for automatically launching mysql on login. Read the output of the above command carefully, as there are a few more steps that won’t be covered here today that are required to initialize and setup your new mysql database. If you don’t have homebrew installed on your mac, you can get it by opening the terminal app and using this command: Homebrew is a unix-style package manager for OS X it’s awesome!
#Mysql os x database location install
I’m a big fan of homebrew, so I used it to install mysql. I couldn’t find a recent, up-to-date faq for doing this, so I thought I would write what I did. I’d like the mysqld process to run as a daemon in the background after the server boots that way I don’t have to log in and start the process after each server reboot.
#Mysql os x database location mac
I’ve been doing some work with WordPress and Joomla recently, which led to the need to have mysql up and running on my dev server it’s a mac mini running OS X Mavericks Server.
0 kommentar(er)
