content_image/792424.jpg content_image/792425.jpg content_image/792426.jpg content_image/792427.jpg
• --bind-address= host 

<img src='content_image/792424.jpg'>

Causes the management server to bind to a specific network interface (host name or IP address). This option has no default value. 

• --character-sets-dir 

<img src='content_image/792425.jpg'>

Directory containing character sets. 

• cluster-config-suffix 

<img src='content_image/792426.jpg'>

Override defaults group suffix when reading cluster configuration sections in my.cnf ; used in testing. 

• --config-cache 

<img src='content_image/792427.jpg'>

This option, whose default value is 1  (or TRUE , or ON ), can be used to disable the management server’s configuration cache, so that it reads its configuration from config.ini  every time it starts (see Section 23.3.3, “NDB Cluster Configuration Files” ). You can do this by starting the ndb_mgmd  process with any one of the following options: 

• --config-cache=0 

• --config-cache=FALSE 

• --config-cache=OFF 

• --skip-config-cache 

Using one of the options just listed is effective only if the management server has no stored configuration at the time it is started. If the management server finds any configuration cache files, then the -- config-cache  option or the --skip-config-cache  option is ignored. Therefore, to disable configuration caching, the option should be used the first  time that the management server is started. Otherwise—that is, if you wish to disable configuration caching for a management server that has already  created a configuration cache—you must stop the management server, delete any existing 

