D.2.2. Non-Typed Child Resource Start And Stop Ordering - Red Hat ENTERPRISE LINUX 5 - ADMINISTRATION Manual

4. lvm:2 — This is an LVM resource. All LVM resources are stopped last. lvm:2 (<lvm
name="2" .../>) is stopped before lvm:1; resources within a group of a resource type are
stopped in the reverse order listed in the Service foo portion of /etc/cluster/cluster.conf.
5. lvm:1 — This is an LVM resource. All LVM resources are stopped last. lvm:1 (<lvm
name="1" .../>) is stopped after lvm:2; resources within a group of a resource type are
stopped in the reverse order listed in the Service foo portion of /etc/cluster/cluster.conf.

D.2.2. Non-typed Child Resource Start and Stop Ordering

Additional considerations are required for non-typed child resources. For a non-typed child resource,
starting order and stopping order are not explicitly specified by the Service resource. Instead, starting
order and stopping order are determined according to the order of the child resource in /etc/
cluster.cluster.conf. Additionally, non-typed child resources are started after all typed child
resources and stopped before any typed child resources.
For example, consider the starting order and stopping order of the non-typed child resources in
Example D.4, "Non-typed and Typed Child Resource in a
<service name="foo">
<script name="1" .../>
<nontypedresource name="foo"/>
<lvm name="1" .../>
<nontypedresourcetwo name="bar"/>
<ip address="10.1.1.1" .../>
<fs name="1" .../>
<lvm name="2" .../>
</service>
Example D.4. Non-typed and Typed Child Resource in a Service
Non-typed Child Resource Starting Order
Example D.4, "Non-typed and Typed Child Resource in a
In
the following order:
1. lvm:1 — This is an LVM resource. All LVM resources are started first. lvm:1 (<lvm
name="1" .../>) is the first LVM resource started among LVM resources because it is the first
LVM resource listed in the Service foo portion of /etc/cluster/cluster.conf.
2. lvm:2 — This is an LVM resource. All LVM resources are started first. lvm:2 (<lvm
name="2" .../>) is started after lvm:1 because it is listed after lvm:1 in the Service foo
portion of /etc/cluster/cluster.conf.
3. fs:1 — This is a File System resource. If there were other File System resources in Service foo,
they would start in the order listed in the Service foo portion of /etc/cluster/cluster.conf.
4. ip:10.1.1.1 — This is an IP Address resource. If there were other IP Address resources in
Service foo, they would start in the order listed in the Service foo portion of /etc/cluster/
cluster.conf.
Non-typed Child Resource Start and Stop Ordering
Service".
Service", the child resources are started in
99