Oracle 5.0 Reference Manual page 381

This means that a client can connect to Instance Manager with a given user name from any host. To
limit connections so that clients can connect only from the local host, start Instance Manager with the
--bind-address=127.0.0.1
Remote clients will not be able to connect. Local clients can connect like this:
shell> mysql -h 127.0.0.1 -P 2273
To generate a new entry, invoke Instance Manager with the
output to the
shell> mysqlmanager --passwd >> /etc/mysqlmanager.passwd
Creating record for new user.
Enter user name:
Enter password:
Re-type password:
At the prompts, enter the user name and password for the new Instance Manager user. You must enter
the password twice. It does not echo to the screen, so double entry guards against entering a different
password than you intend (if the two passwords do not match, no entry is generated).
The preceding command causes the following line to be added to /etc/mysqlmanager.passwd:
mike:*BBF1F551DD9DD96A01E66EC7DDC073911BAD17BA
Use of the
--password
To work around this, use a command like the following from the command line to generate the
password entry:
shell> mysql -B --skip-column-name \
-e 'SELECT CONCAT("user_name",":",PASSWORD("pass_val"));'
The output from the command can be used an entry in the
4.6.10.5. MySQL Server Instance Status Monitoring
To monitor the status of each guarded server instance, the MySQL Instance Manager attempts to
connect to the instance at regular intervals using the
account with a password of check_connection.
You are not required to create this account for MySQL Server; in fact, it is expected that it will not exist.
Instance Manager can tell that a server is operational if the server accepts the connection attempt but
refuses access for the account by returning a login error. However, these failed connection attempts
are logged by the server to its general query log (see
Instance Manager also attempts a connection to nonguarded server instances when you use the
SHOW INSTANCES
nonguarded instances.
Instance Manager knows if a server instance fails at startup because it receives a status from the
attempt. For an instance that starts but later crashes, Instance Manager receives a signal because it is
the parent process of the instance.
4.6.10.6. Connecting to MySQL Instance Manager
mysqlmanager
[355]
/etc/mysqlmanager.passwd
mike
mikepass
mikepass
option fails if
Important
MySQL Instance Manager is been deprecated in MySQL 5.1 and is removed in
MySQL 5.5.
or
SHOW INSTANCE STATUS
Important
MySQL Instance Manager is been deprecated in MySQL 5.1 and is removed in
MySQL 5.5.
— The MySQL Instance Manager
option so that it listens only to the local network interface.
--passwd
file. Here is an example:
is invoked directly from an IBM 5250 terminal.
mysqlmanager
/etc/mysqlmanager.passwd
MySQL_Instance_Manager@localhost
Section 5.2.2, "The General Query
command. This is the only status monitoring done for
361
[356] option and append the
file.
Log").
user