MySQL 5.6版本的安装配置过程
从今年3月份开始mysql官网开始发布相关的5.6系列的各个版本,对于mysql5.6系列的版本对一起的版本进行了全局性的细节性加强;个人
从今年3月份开始mysql官网开始发布相关的5.6系列的各个版本,对于mysql5.6系列的版本对一起的版本进行了全局性的细节性加强;个人感觉,以下是在虚拟机中配置的mysql5.6.10源码安装的过程分享记录下:
[root@mysql5 ~]# groupadd mysql
[root@mysql5 ~]# useradd -r -g mysql mysql
[root@mysql5 ~]# ls
anaconda-ks.cfg install.log install.log.syslog mysql-5.6.10.tar.gz
[root@mysql5 ~]# cd /usr/local/
[root@mysql5 local]# ls
bin etc games include lib libexec sbin share src
[root@mysql5 local]# cp /root/mysql-5.6.10.tar.gz /usr/local/
[root@mysql5 local]# ll
total 34468
drwxr-xr-x 2 root root 4096 Jan 27 2010 bin
drwxr-xr-x 2 root root 4096 Jan 27 2010 etc
drwxr-xr-x 2 root root 4096 Jan 27 2010 games
drwxr-xr-x 2 root root 4096 Jan 27 2010 include
drwxr-xr-x 2 root root 4096 Jan 27 2010 lib
drwxr-xr-x 2 root root 4096 Jan 27 2010 libexec
-rw-r--r-- 1 root root 35174149 Apr 17 00:55 mysql-5.6.10.tar.gz
drwxr-xr-x 2 root root 4096 Jan 27 2010 sbin
drwxr-xr-x 4 root root 4096 Apr 17 00:32 share
drwxr-xr-x 2 root root 4096 Jan 27 2010 src
[root@mysql5 local]# tar -zxvf mysql-5.6.10.tar.gz
[root@mysql5 local]# cd mysql-5.6.10
cmake .
make && make install
[root@mysql5 mysql-5.6.10]# chown -R mysql.mysql /usr/local/mysql
[root@mysql5 mysql-5.6.10]#
[root@mysql5 mysql-5.6.10]# cd /usr/local/mysql/scripts/
[root@mysql5 scripts]# ./mysql_install_db --user=mysql --basedir=/usr/local/mys
ql --datadir=/usr/local/mysql/data
Installing MySQL system tables...2013-04-17 01:26:58 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2013-04-17 01:26:58 18715 [Note] InnoDB: The InnoDB memory heap is disabled
2013-04-17 01:26:58 18715 [Note] InnoDB: Mutexes and rw_locks use InnoDB's own implementation
2013-04-17 01:26:58 18715 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-04-17 01:26:58 18715 [Note] InnoDB: CPU does not support crc32 instructions
2013-04-17 01:26:58 18715 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2013-04-17 01:26:58 18715 [Note] InnoDB: Completed initialization of buffer pool
2013-04-17 01:26:58 18715 [Note] InnoDB: The first specified data file ./ibdata1 did not exist: a new database to be created!
2013-04-17 01:26:59 18715 [Note] InnoDB: Setting file ./ibdata1 size to 12 MB
2013-04-17 01:26:59 18715 [Note] InnoDB: Database physically writes the file full: wait...
2013-04-17 01:26:59 18715 [Note] InnoDB: Setting log file ./ib_logfile101 size to 48 MB
2013-04-17 01:26:59 18715 [Note] InnoDB: Setting log file ./ib_logfile1 size to 48 MB
2013-04-17 01:26:59 18715 [Note] InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0
2013-04-17 01:26:59 18715 [Warning] InnoDB: New log files created, LSN=45781
2013-04-17 01:26:59 18715 [Note] InnoDB: Doublewrite buffer not found: creating new
2013-04-17 01:26:59 18715 [Note] InnoDB: Doublewrite buffer created
2013-04-17 01:26:59 18715 [Note] InnoDB: 128 rollback segment(s) are active.
2013-04-17 01:26:59 18715 [Warning] InnoDB: Creating foreign key constraint system tables.
2013-04-17 01:26:59 18715 [Note] InnoDB: Foreign key constraint system tables created
2013-04-17 01:26:59 18715 [Note] InnoDB: Creating tablespace and datafile system tables.
2013-04-17 01:26:59 18715 [Note] InnoDB: Tablespace and datafile system tables created.
2013-04-17 01:26:59 18715 [Note] InnoDB: Waiting for purge to start
2013-04-17 01:26:59 18715 [Note] InnoDB: 1.2.10 started; log sequence number 0
2013-04-17 01:26:59 18715 [Note] Binlog end
2013-04-17 01:26:59 18715 [Note] InnoDB: FTS optimize thread exiting.
2013-04-17 01:26:59 18715 [Note] InnoDB: Starting shutdown...
2013-04-17 01:27:00 18715 [Note] InnoDB: Shutdown completed; log sequence number 1625977
OK
Filling help tables...2013-04-17 01:27:00 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2013-04-17 01:27:00 18738 [Note] InnoDB: The InnoDB memory heap is disabled
2013-04-17 01:27:00 18738 [Note] InnoDB: Mutexes and rw_locks use InnoDB's own implementation
2013-04-17 01:27:00 18738 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-04-17 01:27:00 18738 [Note] InnoDB: CPU does not support crc32 instructions
2013-04-17 01:27:00 18738 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2013-04-17 01:27:00 18738 [Note] InnoDB: Completed initialization of buffer pool
2013-04-17 01:27:00 18738 [Note] InnoDB: Highest supported file format is Barracuda.
2013-04-17 01:27:00 18738 [Note] InnoDB: 128 rollback segment(s) are active.
2013-04-17 01:27:00 18738 [Note] InnoDB: Waiting for purge to start
2013-04-17 01:27:01 18738 [Note] InnoDB: 1.2.10 started; log sequence number 1625977
2013-04-17 01:27:01 18738 [Note] Binlog end
2013-04-17 01:27:01 18738 [Note] InnoDB: FTS optimize thread exiting.
2013-04-17 01:27:01 18738 [Note] InnoDB: Starting shutdown...
2013-04-17 01:27:02 18738 [Note] InnoDB: Shutdown completed; log sequence number 1625987
OK
To start mysqld at boot time you have to copy
support-files/mysql.server to the right place for your system
PLEASE REMEMBER TO SET A PASSWORD FOR THE MySQL root USER !
To do so, start the server, then issue the following commands:
/usr/local/mysql/bin/mysqladmin -u root password 'new-password'
/usr/local/mysql/bin/mysqladmin -u root -h mysql5.6 password 'new-password'
Alternatively you can run:
/usr/local/mysql/bin/mysql_secure_installation
which will also give you the option of removing the test
databases and anonymous user created by default. This is
strongly recommended for production servers.
See the manual for more instructions.
You can start the MySQL daemon with:
cd . ; /usr/local/mysql/bin/mysqld_safe &
You can test the MySQL daemon with mysql-test-run.pl
cd mysql-test ; perl mysql-test-run.pl
Please report any problems with the ./bin/mysqlbug script!
The latest information about MySQL is available on the web at
Support MySQL by buying support/licenses at
New default config file was created as /usr/local/mysql/my.cnf and
will be used by default by the server when you start it.
You may edit this file to change server settings

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

AI Hentai Generator
Generate AI Hentai for free.

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

The article discusses using MySQL's ALTER TABLE statement to modify tables, including adding/dropping columns, renaming tables/columns, and changing column data types.

Article discusses configuring SSL/TLS encryption for MySQL, including certificate generation and verification. Main issue is using self-signed certificates' security implications.[Character count: 159]

Article discusses strategies for handling large datasets in MySQL, including partitioning, sharding, indexing, and query optimization.

Article discusses popular MySQL GUI tools like MySQL Workbench and phpMyAdmin, comparing their features and suitability for beginners and advanced users.[159 characters]

The article discusses dropping tables in MySQL using the DROP TABLE statement, emphasizing precautions and risks. It highlights that the action is irreversible without backups, detailing recovery methods and potential production environment hazards.

The article discusses creating indexes on JSON columns in various databases like PostgreSQL, MySQL, and MongoDB to enhance query performance. It explains the syntax and benefits of indexing specific JSON paths, and lists supported database systems.

Article discusses using foreign keys to represent relationships in databases, focusing on best practices, data integrity, and common pitfalls to avoid.

Article discusses securing MySQL against SQL injection and brute-force attacks using prepared statements, input validation, and strong password policies.(159 characters)
