diff --git a/src/pacemaker/man/index.php b/src/pacemaker/man/index.php index edac999..169bf27 100644 --- a/src/pacemaker/man/index.php +++ b/src/pacemaker/man/index.php @@ -1,214 +1,194 @@ --- layout: pacemaker title: Pacemaker Manual Pages ---

Pacemaker Command Line Tools

Tool Summary

DESCRIPTION')) { - $line = fgets($file_handle); - $line = fgets($file_handle); - while (!feof($file_handle)) { - $line = fgets($file_handle); - if(strstr($line, 'OPTIONS')) { - $done = 1; - break; - - } else { - echo $line; - } - } - if($done) { - break; - } + /* Show everything in the description section (which ends with the next + second-level heading or some magic strings for specific nonstandard + man pages). + */ + while (!feof($file_handle) && !$done) { + $line = fgets($file_handle); + if (strstr($line, 'h2>DESCRIPTION')) { + $line = fgets($file_handle); + $line = fgets($file_handle); + while (!feof($file_handle) && !$done) { + $line = fgets($file_handle); + if (strstr($line, '

') + || strstr($line, 'usage:') + || strstr($line, 'Common') + ) { + $done = 1; + } else { + echo $line; + } + } + } } -} -fclose($file_handle); + fclose($file_handle); } - $mans = glob("*.8.html"); +$mans = glob("*.8.html"); foreach ($mans as $m) { $fields = explode(".", $m, 3); $base = $fields[0]; - echo '
'; echo ''; echo "$base"; echo ''; echo ''; get_desc($m); echo ''; echo '
'; } ?>

The Right Tool for the Job

- Pacemaker ships with a comprehensive set of tools that assist you - in managing your cluster from the command line. Here we introduce - the tools needed for managing the cluster configuration in the - CIB and the cluster resources. -

-

- The following list presents several tasks related to cluster - management and briefly introduces the tools to use to - accomplish these tasks: + Pacemaker ships with a set of command-line tools to assist you + in managing your cluster. Their manual pages are all linked + above. Here are more details about the most important tools:

-
- Monitoring the Cluster's Status -
-
-

The crm_mon command - allows you to monitor your cluster's status and - configuration. Its output includes the number of nodes, - uname, uuid, status, the resources configured in your - cluster, and the current status of each. The output of - - crm_mon - - can be displayed at the console or printed into an HTML - file. When provided with a cluster configuration file - without the status section, - - crm_mon - - creates an overview of nodes and resources as specified - in the file. See crm_mon(8) - for a detailed introduction to this tool's usage and - command syntax. -

-
-
- Managing the CIB +
+ Monitoring Cluster Status +
+
+

The crm_mon command + allows you to monitor your cluster's status and + configuration. Its output includes the number of nodes, + uname, uuid, status, the resources configured in your + cluster, and the current status of each. The output of + crm_mon + can be displayed at the console or printed into an XML or HTML + file. When provided with a cluster configuration file + without the status section, + crm_mon + creates an overview of nodes and resources as specified + in the file. See crm_mon(8) + for a detailed introduction to this tool's usage and + command syntax. +

+
+
+ Managing the Cluster Configuration

The cibadmin command is the low-level administrative command for manipulating the Pacemaker CIB. It can be used to dump all or part of the CIB, update all or part of it, modify all or part of it, delete the entire CIB, or perform miscellaneous CIB administrative operations. See cibadmin(8) for a detailed introduction to this tool's usage and command syntax.

-
-
- Managing Configuration Changes -
-

The crm_diff command assists you in creating and applying XML patches. This can be useful for visualizing the changes between two versions of the cluster configuration or saving changes so they can be applied at a later time using cibadmin(8). See crm_diff(8) for a detailed introduction to this tool's usage and command syntax.

-
-
- Manipulating CIB Attributes -
-
-

The crm_attribute - command lets you query and manipulate node attributes - and cluster configuration options that are used in the - CIB. See crm_attribute(8) - for a detailed introduction to this tool's usage and - command syntax.

-
-
- Validating the Cluster Configuration -
-

The crm_verify command checks the configuration database (CIB) for consistency and other problems. It can check a file containing the configuration or connect to a running cluster. It reports two classes of problems. Errors must be fixed before Pacemaker can work properly while warning resolution is up to the administrator. crm_verify assists in creating new or modified configurations. You can take a local copy of a CIB in the running cluster, edit it, validate it using crm_verify , then put the new configuration into effect using cibadmin . See crm_verify(8) for a detailed introduction to this tool's usage and command syntax.

- Managing Resource Configurations + Manipulating Attributes +
+
+

The crm_attribute + command lets you query and manipulate node attributes + and cluster configuration options that are used in the + CIB. See crm_attribute(8) + for a detailed introduction to this tool's usage and + command syntax.

+
+
+ Managing Resources

The crm_resource command performs various resource-related actions on the cluster. It lets you modify the definition of configured resources, start and stop resources, or delete and migrate resources between nodes. See crm_resource(8) for a detailed introduction to this tool's usage and command syntax.

Managing Resource Fail Counts

The crm_failcount command queries the number of failures per resource on a given node. This tool can also be used to reset the failcount, allowing the resource to again run on nodes where it had failed too often. See crm_failcount(8) for a detailed introduction to this tool's usage and command syntax.

- Managing a Node's Standby Status + Managing Nodes

The crm_standby command can manipulate a node's standby attribute. Any node in standby mode is no longer eligible to host resources and any resources that are there must be moved. Standby mode can be useful for performing maintenance tasks, such as kernel updates. Remove the standby attribute from the node as it should become a fully active member of the cluster again. See crm_standby(8) for a detailed introduction to this tool's usage and command syntax.