mysqlmanager
— The MySQL Instance Manager
360
The permissible options for
[mysqldN]
server instance sections are described in
Section 4.6.10.2,
“MySQL Instance Manager Configuration Files”
. In these sections, you can use a special
mysqld-
path=path-to-mysqld-binary
option that is recognized only by Instance Manager. Use this option
to let Instance Manager know where the
mysqld
binary resides. If there are multiple instances, it may
also be necessary to set other options such as
datadir
and
port
, to ensure that each instance has
a different data directory and TCP/IP port number.
Section 5.3, “Running Multiple MySQL Instances
on One Machine”
, discusses the configuration values that must differ for each instance when you run
multiple instance on the same machine.
Warning
The
[mysqld]
instance section, if it exists, must not contain any Instance
Manager-specific options.
The typical Unix startup/shutdown cycle for a MySQL server with the MySQL Instance Manager
enabled is as follows:
1. The
/etc/init.d/mysql
script starts MySQL Instance Manager.
2. Instance Manager starts the guarded server instances and monitors them.
3. If a server instance fails, Instance Manager restarts it.
4. If Instance Manager is shut down (for example, with the
/etc/init.d/mysql stop
command), it
shuts down all server instances.
4.6.10.4. Instance Manager User and Password Management
Important
MySQL Instance Manager is been deprecated in MySQL 5.1 and is removed in
MySQL 5.5.
The Instance Manager stores its user information in a password file. On Windows, the default is
mysqlmanager.passwd
in the directory where Instance Manager is installed. On Unix, the default
file is
/etc/mysqlmanager.passwd
. To specify a different location for the password file, use the
--
password-file
[357]
option.
If the password file does not exist or contains no password entries, you cannot connect to the Instance
Manager.
Note
Any Instance Manager process that is running to monitor server instances does
not notice changes to the password file. You must stop it and restart it after
making password entry changes.
Entries in the password file have the following format, where the two fields are the account user name
and encrypted password, separated by a colon:
petr:*35110DC9B4D8140F5DE667E28C72DD2597B5C848
Instance Manager password encryption is the same as that used by MySQL Server. It is a one-way
operation; no means are provided for decrypting encrypted passwords.
Instance Manager accounts differ somewhat from MySQL Server accounts:
• MySQL Server accounts are associated with a host name, user name, and password (see
Section 6.3.1, “User Names and Passwords”
).
• Instance Manager accounts are associated with a user name and password only.
Содержание 5.0
Страница 1: ...MySQL 5 0 Reference Manual ...
Страница 18: ...xviii ...
Страница 60: ...40 ...
Страница 396: ...376 ...
Страница 578: ...558 ...
Страница 636: ...616 ...
Страница 844: ...824 ...
Страница 1234: ...1214 ...
Страница 1426: ...MySQL Proxy Scripting 1406 The following diagram shows an overview of the classes exposed by MySQL Proxy ...
Страница 1427: ...MySQL Proxy Scripting 1407 ...
Страница 1734: ...1714 ...
Страница 1752: ...1732 ...
Страница 1783: ...Configuring Connector ODBC 1763 ...
Страница 1793: ...Connector ODBC Examples 1773 ...
Страница 1839: ...Connector Net Installation 1819 2 You must choose the type of installation to perform ...
Страница 1842: ...Connector Net Installation 1822 5 Once the installation has been completed click Finish to exit the installer ...
Страница 1864: ...Connector Net Visual Studio Integration 1844 Figure 20 24 Debug Stepping Figure 20 25 Function Stepping 1 of 2 ...
Страница 2850: ...2830 ...
Страница 2854: ...2834 ...
Страница 2928: ...2908 ...
Страница 3000: ...2980 ...
Страница 3122: ...3102 ...
Страница 3126: ...3106 ...
Страница 3174: ...3154 ...
Страница 3232: ...3212 ...