Oracle 5.0 Reference Manual page 379

Here are some sample instance sections:
[mysqld1]
mysqld-path=/usr/local/mysql/libexec/mysqld
socket=/tmp/mysql.sock
port=3307
server_id=1
skip-stack-trace
core-file
skip-bdb
log-bin
log-error
log=mylog
log-slow-queries
[mysqld2]
nonguarded
port=3308
server_id=2
mysqld-path= /home/cps/mysql/trees/mysql-5.0/sql/mysqld
socket = /tmp/mysql.sock5
pid-file = /tmp/hostname.pid5
datadir= /home/cps/mysql_data/data_dir1
language=/home/cps/mysql/trees/mysql-5.0/sql/share/english
log-bin
log=/tmp/fordel.log
4.6.10.3. Starting the MySQL Server with MySQL Instance Manager
This section discusses how Instance Manager starts server instances when it starts. However, before
you start Instance Manager, you should set up a password file for it. Otherwise, you will not be able to
connect to Instance Manager to control it after it starts. For details about creating Instance Manager
accounts, see
On Unix, the
script, which usually resides in the
mysqlmanager
the
mysqld_safe
startup script was changed again to incorporate both setup schemes. In version 5.0.4, the startup script
uses the old scheme (invoking mysqld_safe) by default, but one can set the
variable in the script to
Starting with MySQL 5.0.19, you can use Instance Manager if you modify the
by adding
use-manager
[mysql.server]
use-manager
When Instance Manager starts, it reads its configuration file if it exists to find server instance sections
and prepare a list of instances. Instance sections have names of the form
where is an unsigned integer (for example, [mysqld1], [mysqld2], and so forth).
N
After preparing the list of instances, Instance Manager starts the guarded instances in the list. If there
are no instances, Instance Manager creates an instance named
with default (compiled-in) configuration values. This means that the Instance Manager cannot find
the
mysqld
describes default locations for components of MySQL distributions.) If you have installed the MySQL
server in a nonstandard location, you should create the Instance Manager configuration file.
Instance Manager also stops all guarded server instances when it shuts down.
mysqlmanager
Important
MySQL Instance Manager is been deprecated in MySQL 5.1 and is removed in
MySQL 5.5.
Section 4.6.10.4, "Instance Manager User and Password
MySQL database server normally is started with the
mysqld
/etc/init.d/
(the MySQL Instance Manager binary) to start MySQL. (In prior versions of MySQL
script is used for this purpose.) Starting from MySQL 5.0.4, the behavior of the
(zero) to use the MySQL Instance Manager to start a server.
0
to the
[mysql.server]
program if it is not installed in the default location.
— The MySQL Instance Manager
directory. In MySQL 5.0.3, this script invokes
section:
359
Management".
mysql.server
use_mysqld_safe
my.cnf
or [mysqldN],
[mysqld]
and attempts to start it
mysqld
(Section 2.7, "Installation
configuration file
Layouts",