Chapter 6. Configuration

Both tacoplexadm and tacoplexd depend on the values specified in tacoplex.conf. By default, they look for this file in /etc but its location can be specified to either executable on the command-line via the -f option. For example:

% tacoplexd -f /var/tacoplex/taco.conf &

would start up tacoplexd and attempt to read configuration data from the file /var/tacoplex/taco.conf. The example file included with the distribution lists and documents all of the available directives and options. Lines beginning with a "#" are comments.

Configuring mon can be as simple or as complicated as your monitoring needs require. The mon documentation is complete and authoritative. The TacoPleX distribution includes a sample mon.cf file that utilizes tacoplex.monitor and does some simple logging of detected errors. You can expand from this baseline to include email or paging notification and additional monitors for resources not directly part of TacoPleX (e.g. routers).

Each leveler in a cluster has separate configuration files. It is possible (but not recommended) to configure each leveler differently. The right combination of differences can lead to system failures. Critical points of configuration are documented in the supplied tacoplex.conf file. If possible, it is best to maintain the same configuration across all of your levelers.