You should keep the following issues and notes in mind:
OS X 10.4 deprecated startup items in favor of launchd daemons, and as of OS X 10.10 (Yosemite), startup items do not function. For these reasons, using launchd daemons is preferred over startup items.
You may need (or want) to create a specific
mysql user to own the MySQL directory and
data. You can do this through the Directory
Utility, and the
should already exist. For use in single user mode, an entry
_mysql (note the underscore prefix)
should already exist within the system
If you get an “insecure startup item disabled” error when MySQL launches, use the following procedure. Adjust the pathnames appropriately for your system.
Modify the mysql.script using this command (enter it on a single line):
Locate the option file that defines the
basedir value and modify it to contain
directory, make the following group ID changes from
sudo chgrp wheel MySQLCOM StartupParameters.plist
Start the server from System Preferences or Terminal.app.
Because the MySQL package installer installs the MySQL
contents into a version and platform specific directory, you
can use this to upgrade and migrate your database between
versions. You will need to either copy the
data directory from the old version to
the new version, or alternatively specify an alternative
datadir value to set location of the data
directory. By default, the MySQL directories are installed
You might want to add aliases to your shell's resource file to make it easier to access commonly used programs such as mysql and mysqladmin from the command line. The syntax for bash is:
alias mysql=/usr/local/mysql/bin/mysql alias mysqladmin=/usr/local/mysql/bin/mysqladmin
For tcsh, use:
alias mysql /usr/local/mysql/bin/mysql alias mysqladmin /usr/local/mysql/bin/mysqladmin
Even better, add
PATH environment variable. You can do
this by modifying the appropriate startup file for your shell.
For more information, see Invoking MySQL Programs.
After you have copied over the MySQL database files from the
previous installation and have successfully started the new
server, you should consider removing the old installation
files to save disk space. Additionally, you should also remove
older versions of the Package Receipt directories located in