5.4.1. Starting the MySQL Server with MySQL Instance Manager
Normally, the mysqld MySQL Database Server
is started with the mysql.server script,
which usually resides in the /etc/init.d/
folder. This script invokes the mysqld_safe
script by default. However, you can set the
use_mysqld_safe variable in the script to
0 (zero) to use the MySQL Instance Manager
to start a server.
The Instance Manager's behavior in this case depends on the
options given in the MySQL configuration file. If there is no
configuration file, the MySQL Instance Manager creates a
server instance named mysqld and attempts
to start it with default (compiled-in) configuration values.
This means that the IM cannot guess the placement of
mysqld if it is not installed in the
default location. If you have installed the MySQL server in a
non-standard location, you should use a configuration file.
See Section 2.1.5, “Installation Layouts”.
If there is a configuration file, the IM reads it to find
[mysqld] sections (for example,
[mysqld], [mysqld1],
[mysqld2], and so forth). Each such section
specifies an instance. When it starts, the Instance Manager
attempts to start all server instances that it finds. By
default, the Instance Manager stops all server instances when
it shuts down.
Note that there is a special
--mysqld-path=path-to-mysqld-binary
option that is recognized only by the IM. Use this variable to
let the IM know where the mysqld binary
resides. You should also set basedir and
datadir options for the server.
The typical startup/shutdown cycle for a MySQL server with the
MySQL Instance Manager enabled is as follows:
The MySQL Instance Manager is started with
/etc/init.d/mysql script.
The MySQL Instance Manager starts all instances and
monitors them.
If a server instance fails the MySQL Instance Manager
restarts it.
If the MySQL Instance Manager is shut down (for instance
with the /etc/init.d/mysql stop
command), all instances are shut down by the MySQL
Instance Manager.
