Oracle 5.0 Reference Manual page 376

mysqlmanager
The IP address to bind to.
•
--default-mysqld-path=path
The path name of the MySQL Server binary. This path name is used for all server instance sections
in the configuration file for which no
option is the compiled-in path name, which depends on how the MySQL distribution was configured.
Example:
--default-mysqld-path=/usr/sbin/mysqld
•
--defaults-file=file_name
Read Instance Manager and MySQL Server settings from the given file. All configuration changes
made by the Instance Manager will be written to this file. This must be the first option on the
command line if it is used, and the file must exist.
If this option is not given, Instance Manager uses its standard configuration file. On Windows, the
standard file is
my.ini
file is /etc/my.cnf.
• [356]
--install
On Windows, install Instance Manager as a Windows service. The service name is
Manager. This option was added in MySQL 5.0.11.
•
--log=file_name
The path to the Instance Manager log file. This option has no effect unless the
[357] option is also given. If the file name specified for the option is a relative name, the
service
log file is created under the directory from which Instance Manager is started. To ensure that the file
is created in a specific directory, specify it as a full path name.
If
--run-as-service
the data directory.
If
--run-as-service
output, you can redirect Instance Manager output to a file:
mysqlmanager > im.log
•
--monitoring-interval=seconds
The interval in seconds for monitoring server instances. The default value is 20 seconds.
Instance Manager tries to connect to each monitored (guarded) instance using the nonexisting
MySQL_Instance_Manager
of the connection attempt indicates that the instance is unavailable, Instance Manager performs
several attempts to restart the instance.
Normally, the
MySQL_Instance_Manager
Instance Manager cause the monitored instance to produce messages in its general query log similar
to the following:
Access denied for user 'MySQL_Instance_M'@'localhost' (using password: YES)
The option in the appropriate server instance section disables monitoring for a
nonguarded
particular instance. If the instance dies after being started, Instance Manager will not restart it.
Instance Manager tries to connect to a nonguarded instance only when you request the instance's
status (for example, with the
See Section 4.6.10.5, "MySQL Server Instance Status
• [356],
--passwd -P
— The MySQL Instance Manager
[356]
mysqld-path
[356]
in the directory where Instance Manager is installed. On Unix, the standard
[356]
[357] is given without
[357] is not given, log messages go to the standard output. To capture log
[356]
user account to check whether it is available/not hanging. If the result
account does not exist, so the connection attempts by
SHOW INSTANCES
356
option is present. The default value of this
[356]
[356], the log file is
--log
status.
Monitoring", for more information.
MySQL
--run-as-
in
mysqlmanager.log