Appendix D. Modifying and Enforcing Cluster Service Resource Actions
meta-dataaction). You can override these defaults with explicit
<action>specifications in the
- For the
stopactions, you may want to modify the
- For the
statusaction, you may want to modify the
depthproperties. For information on the
statusaction and its properties, see Section D.1, “Modifying the Resource Status Check Interval”.
timeoutproperty for an action is enforced only if you explicitly configure timeout enforcement, as described in Section D.2, “Enforcing Resource Timeouts”.
cluster.conffile to modify a resource action parameter, see Section D.1, “Modifying the Resource Status Check Interval”.
/etc/cluster/cluster.conf. For a comprehensive list and description of
cluster.confelements and attributes, see the cluster schema at
/usr/share/cluster/cluster.rng, and the annotated schema at
D.1. Modifying the Resource Status Check Interval
cluster.conffile using the special
<action name="status" depth="*" interval="10" />
cluster.conffile. For example, if you had a file system resource for which you wanted to override the status check interval you could specify the file system resource in the
cluster.conffile as follows:
<fs name="test" device="/dev/sdb3"> <action name="status" depth="*" interval="10" /> <nfsexport...> </nfsexport> </fs>
depthis set to
*, which indicates that these values should be used for all depths. The result is that the
testfile system is checked at the highest-defined depth provided by the resource-agent (in this case, 20) every 10 seconds.