Table of Contents [+/-]
MySQL 5.5 supports Solaris 10 (Update 11 and later), and Solaris 11 (Update 3 and later).
MySQL on Solaris is available in a number of different formats.
For information on installing using the native Solaris PKG format, see Section 8.1, “Installing MySQL on Solaris Using a Solaris PKG”.
To use a standard
tarbinary installation, use the notes provided in Chapter 3, Installing MySQL on Unix/Linux Using Generic Binaries. Check the notes and hints at the end of this section for Solaris specific notes that you may need before or after installation.
To obtain a binary MySQL distribution for Solaris in tarball or PKG format, https://dev.mysql.com/downloads/mysql/5.5.html.
Additional notes to be aware of when installing and using MySQL on Solaris:
If you want to use MySQL with the
mysqluser and group, use the groupadd and useradd commands:
groupadd mysql useradd -g mysql -s /bin/false mysql
If you install MySQL using a binary tarball distribution on Solaris, because the Solaris tar cannot handle long file names, use GNU tar (gtar) to unpack the distribution. If you do not have GNU tar on your system, install it with the following command:
pkg install archiver/gnu-tar
You should mount any file systems on which you intend to store
InnoDBfiles with the
forcedirectiooption. (By default mounting is done without this option.) Failing to do so will cause a significant drop in performance when using the
InnoDBstorage engine on this platform.
If you would like MySQL to start automatically, you can copy
/etc/init.dand create a symbolic link to it named
If too many processes try to connect very rapidly to mysqld, you should see this error in the MySQL log:
Error in accept: Protocol error
You might try starting the server with the
--back_log=50option as a workaround for this.
To configure the generation of core files on Solaris you should use the coreadm command. Because of the security implications of generating a core on a
setuid()application, by default, Solaris does not support core files on
setuid()programs. However, you can modify this behavior using coreadm. If you enable
setuid()core files for the current user, they will be generated using the mode 600 and owned by the superuser.