mysql5.5 version and version 5.6 on the same server to open the instance, in daily work will encounter, open multi-version need to note:
1. Startup initialization cannot be initialized with the name of the Ln-s link.
2, start need to add--ledir=basedir
3, start filling in the parameters of the location
650) this.width=650; "Src=" Http://s4.51cto.com/wyfs02/M01/89/F4/wKiom1gimTvDhKYEAABbp7uy98c633.png-wh_500x0-wm_3 -wmp_4-s_2779627771.png "title=" Dddd.png "alt=" Wkiom1gimtvdhkyeaabbp7uy98c633.png-wh_50 "/>
Before that, always use ln-s to start the 5.6 error:
650) this.width=650; "Src=" Http://s4.51cto.com/wyfs02/M01/89/F0/wKioL1gimcjy-IboAADXVQDWk4E328.png-wh_500x0-wm_3 -wmp_4-s_290518295.png "title=" 44444.png "alt=" Wkiol1gimcjy-iboaadxvqdwk4e328.png-wh_50 "/>
Before that, look at the boot, right?
650) this.width=650; "Src=" Http://s3.51cto.com/wyfs02/M02/89/F4/wKiom1gimkCRRfJZAAAm7OJuUTo308.png-wh_500x0-wm_3 -wmp_4-s_2520343615.png "title=" 66666.png "alt=" Wkiom1gimkcrrfjzaaam7ojuuto308.png-wh_50 "/>
However the displayed unknown variable ' defaults-file=/etc/my3309.cnf '
At the same time, depending on the configuration of the configuration file, error path is not correct, will default to/var/log/mysql.log ....
The right way is:
Initialization
/usr/local/mysql-xxx-linux-glibcxx-x86_64/scripts/mysql_install_db--user=mysql--basedir=/usr/local/ mysql-xxx-linux-glibcxx-x86_64/--datadir=/data/mysql3309/mysql3309/--defaults-file=/etc/my3309.cnf (this uses ln- s after alias OK)
Start command:
/usr/local/mysql56/bin/mysqld_safe--defaults-file=/etc/my3309.cnf--datadir=/data/mysql3309/mysql3309/--basedir =/usr/local/mysql-xxx-linux-glibcxx-x86_64--user=mysql--ledir=/usr/local/mysql-xxxx-linux-glibcxxx-x86_64/bin &
Then just ok .... What the network said about the 5.5 of what configuration file coverage, seemingly ripped ...
This article is from the "DBSpace" blog, so be sure to keep this source http://dbspace.blog.51cto.com/6873717/1871014
MySQL binary package Installation instance (5.5, 5.6 coexistence)