mysqlmanager
— The MySQL Instance Manager
356
The IP address to bind to.
•
--default-mysqld-path=path
[356]
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
mysqld-path
option is present. The default value of this
option is the compiled-in path name, which depends on how the MySQL distribution was configured.
Example:
--default-mysqld-path=/usr/sbin/mysqld
[356]
•
--defaults-file=file_name
[356]
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
in the directory where Instance Manager is installed. On Unix, the standard
file is
/etc/my.cnf
.
•
--install
[356]
On Windows, install Instance Manager as a Windows service. The service name is
MySQL
Manager
. This option was added in MySQL 5.0.11.
•
--log=file_name
[356]
The path to the Instance Manager log file. This option has no effect unless the
--run-as-
service
[357]
option is also given. If the file name specified for the option is a relative name, the
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
[357]
is given without
--log
[356]
, the log file is
mysqlmanager.log
in
the data directory.
If
--run-as-service
[357]
is not given, log messages go to the standard output. To capture log
output, you can redirect Instance Manager output to a file:
mysqlmanager > im.log
•
--monitoring-interval=seconds
[356]
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
user account to check whether it is available/not hanging. If the result
of the connection attempt indicates that the instance is unavailable, Instance Manager performs
several attempts to restart the instance.
Normally, the
MySQL_Instance_Manager
account does not exist, so the connection attempts by
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
nonguarded
option in the appropriate server instance section disables monitoring for a
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
SHOW INSTANCES
status.
See
Section 4.6.10.5, “MySQL Server Instance Status Monitoring”
, for more information.
•
--passwd
[356]
,
-P
Summary of Contents for 5.0
Page 1: ...MySQL 5 0 Reference Manual ...
Page 18: ...xviii ...
Page 60: ...40 ...
Page 396: ...376 ...
Page 578: ...558 ...
Page 636: ...616 ...
Page 844: ...824 ...
Page 1234: ...1214 ...
Page 1427: ...MySQL Proxy Scripting 1407 ...
Page 1734: ...1714 ...
Page 1752: ...1732 ...
Page 1783: ...Configuring Connector ODBC 1763 ...
Page 1793: ...Connector ODBC Examples 1773 ...
Page 1839: ...Connector Net Installation 1819 2 You must choose the type of installation to perform ...
Page 2850: ...2830 ...
Page 2854: ...2834 ...
Page 2928: ...2908 ...
Page 3000: ...2980 ...
Page 3122: ...3102 ...
Page 3126: ...3106 ...
Page 3174: ...3154 ...
Page 3232: ...3212 ...