Installation guide

Example D.6 . Service foo No rmal Failu re Reco very
<service name="foo">
<script name="script_one" ...>
<script name="script_two" .../>
</script>
<script name="script_three" .../>
</service>
Example D.7. Service foo Failu re Reco very wit h __independent_subtree At t rib u t e
<service name="foo">
<script name="script_one" __independent_subtree="1" ...>
<script name="script_two" __independent_subtree="1" .../>
<script name="script_three" .../>
</script>
<script name="script_four" .../>
</service>
In some circumstances, if a component of a service fails you may want to disable only that
component without disabling the entire service, to avoid affecting other services the use other
components of that service. As of the Red Hat Enterprise Linux 5.6 release, you can accomplish that
by using the __independent_subtree="2" attribute, which designates the independent subtree
as non-critical.
Note
You may only use the non-critical flag on singly-referenced resources. The non-critical flag
works with all resources at all levels of the resource tree, but should not be used at the top
level when defining services or virtual machines.
As of the Red Hat Enterprise Linux 5.6 release, you can set maximum restart and restart expirations
on a per-node basis in the resource tree for independent subtrees. To set these thresholds, you can
use the following attributes:
__max_restarts configures the maximum number of tolerated restarts prior to giving up.
__restart_expire_time configures the amount of time, in seconds, after which a restart is no
longer attempted.
D.5. Debugging and T est ing Services and Resource Ordering
You can debug and test services and resource ordering with the rg_test utility. rg_test is a
command-line utility that is run from a shell or a terminal (it is not available in Co n g a or system-
config-cluster.) Table D.2, “ rg_test Utility Summary summarizes the actions and syntax for
the rg_test utility.
T ab le D.2. rg_test Ut ilit y Su mmary
HA Resou rce Behavior
117