[root@mysql- mysql]# service mysqld strat

用法：/etc/init.d/mysqld {start|stop|status|restart|condrestart|try-restart|reload|force-reload}

[root@mysql- mysql]# service mysqld start

初始化 MySQL 数据库： -- ::  [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).

-- ::  [Note] /usr/sbin/mysqld (mysqld 5.6.) starting as process  ...

-- ::  [Note] InnoDB: Using atomics to ref count buffer pool pages

-- ::  [Note] InnoDB: The InnoDB memory heap is disabled

-- ::  [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins

-- ::  [Note] InnoDB: Memory barrier is not used

-- ::  [Note] InnoDB: Compressed tables use zlib 1.2.

-- ::  [Note] InnoDB: Using Linux native AIO

-- ::  [Note] InnoDB: Using CPU crc32 instructions

-- ::  [Note] InnoDB: Initializing buffer pool, size = 128.0M

-- ::  [Note] InnoDB: Completed initialization of buffer pool

-- ::  [Note] InnoDB: The first specified data file ./ibdata1 did not exist: a new database to be created!

-- ::  [Note] InnoDB: Setting file ./ibdata1 size to  MB

-- ::  [Note] InnoDB: Database physically writes the file full: wait...

-- ::  [Note] InnoDB: Setting log file ./ib_logfile101 size to  MB

-- ::  [Note] InnoDB: Setting log file ./ib_logfile1 size to  MB

-- ::  [Note] InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0

-- ::  [Warning] InnoDB: New log files created, LSN=

-- ::  [Note] InnoDB: Doublewrite buffer not found: creating new

-- ::  [Note] InnoDB: Doublewrite buffer created

-- ::  [Note] InnoDB:  rollback segment(s) are active.

-- ::  [Warning] InnoDB: Creating foreign key constraint system tables.

-- ::  [Note] InnoDB: Foreign key constraint system tables created

-- ::  [Note] InnoDB: Creating tablespace and datafile system tables.

-- ::  [Note] InnoDB: Tablespace and datafile system tables created.

-- ::  [Note] InnoDB: Waiting for purge to start

-- ::  [Note] InnoDB: 5.6. started; log sequence number

-- ::  [Note] Binlog end

-- ::  [Note] InnoDB: FTS optimize thread exiting.

-- ::  [Note] InnoDB: Starting shutdown...

-- ::  [Note] InnoDB: Shutdown completed; log sequence number 

-- ::  [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).

-- ::  [Note] /usr/sbin/mysqld (mysqld 5.6.) starting as process  ...

-- ::  [Note] InnoDB: Using atomics to ref count buffer pool pages

-- ::  [Note] InnoDB: The InnoDB memory heap is disabled

-- ::  [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins

-- ::  [Note] InnoDB: Memory barrier is not used

-- ::  [Note] InnoDB: Compressed tables use zlib 1.2.

-- ::  [Note] InnoDB: Using Linux native AIO

-- ::  [Note] InnoDB: Using CPU crc32 instructions

-- ::  [Note] InnoDB: Initializing buffer pool, size = 128.0M

-- ::  [Note] InnoDB: Completed initialization of buffer pool

-- ::  [Note] InnoDB: Highest supported file format is Barracuda.

-- ::  [Note] InnoDB:  rollback segment(s) are active.

-- ::  [Note] InnoDB: Waiting for purge to start

-- ::  [Note] InnoDB: 5.6. started; log sequence number

-- ::  [Note] Binlog end

-- ::  [Note] InnoDB: FTS optimize thread exiting.

-- ::  [Note] InnoDB: Starting shutdown...

-- ::  [Note] InnoDB: Shutdown completed; log sequence number 

PLEASE REMEMBER TO SET A PASSWORD FOR THE MySQL root USER !

To do so, start the server, then issue the following commands:

  /usr/bin/mysqladmin -u root password 'new-password'

  /usr/bin/mysqladmin -u root -h mysql- password 'new-password'

Alternatively you can run:

  /usr/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.

Please report any problems at http://bugs.mysql.com/

The latest information about MySQL is available on the web at

  http://www.mysql.com

Support MySQL by buying support/licenses at http://shop.mysql.com

Note: new default config file not created.

Please make sure your config file is current

WARNING: Default config file /etc/my.cnf exists on the system

This file will be read by default by the MySQL server

If you do not want to use this, either remove it, or use the

--defaults-file argument to mysqld_safe when starting the server

                                                           [确定]

正在启动 mysqld：                                          [确定]

[root@mysql- mysql]# /usr/bin/mysql_secure_installation

NOTE: RUNNING ALL PARTS OF THIS SCRIPT IS RECOMMENDED FOR ALL MySQL

      SERVERS IN PRODUCTION USE!  PLEASE READ EACH STEP CAREFULLY!

In order to log into MySQL to secure it, we'll need the current

password for the root user.  If you've just installed MySQL, and

you haven't set the root password yet, the password will be blank,

so you should just press enter here.

Enter current password for root (enter for none):    ----输入root密码（默认为空）：

OK, successfully used password, moving on...

Setting the root password ensures that nobody can log into the MySQL

root user without the proper authorisation.

Set root password? [Y/n] y             ----是否要修改root密码：

New password:

Re-enter new password:

Password updated successfully!

Reloading privilege tables..

 ... Success!

By default, a MySQL installation has an anonymous user, allowing anyone

to log into MySQL without having to have a user account created for

them.  This is intended only for testing, and to make the installation

go a bit smoother.  You should remove them before moving into a

production environment.

Remove anonymous users? [Y/n] y

 ... Success!

Normally, root should only be allowed to connect from 'localhost'.  This

ensures that someone cannot guess at the root password from the network.

Disallow root login remotely? [Y/n] y

 ... Success!

By default, MySQL comes with a database named 'test' that anyone can

access.  This is also intended only for testing, and should be removed

before moving into a production environment.

Remove test database and access to it? [Y/n] n

 ... skipping.

Reloading the privilege tables will ensure that all changes made so far

will take effect immediately.

Reload privilege tables now? [Y/n] y

 ... Success!

All done!  If you've completed all of the above steps, your MySQL

installation should now be secure.

Thanks for using MySQL!

Cleaning up...

[root@mysql- mysql]#