Installation guide

started after nontypedresource:foo. (Non-typed resources are started in the order that
they appear in the Service resource.)
No n-t ype d Child Reso urce St o pping Orde r
In Example D.4, “ Non-typed and Typed Child Resource in a Service” , the child resources are stopped
in the following order:
1. nontypedresourcetwo:bar — This is a non-typed resource. Because it is a non-typed
resource, it is stopped before the typed resources are stopped. In addition, its order in the
Service resource is after the other non-typed resource, nontypedresource:foo; therefore, it
is stopped before nontypedresource:foo. (Non-typed resources are stopped in the
reverse order that they appear in the Service resource.)
2. nontypedresource:foo — This is a non-typed resource. Because it is a non-typed
resource, it is stopped before the typed resources are stopped. In addition, its order in the
Service resource is before the other non-typed resource, nontypedresourcetwo:bar;
therefore, it is stopped after nontypedresourcetwo:bar. (Non-typed resources are
stopped in the reverse order that they appear in the Service resource.)
3. script:1 — This is a Script resource. If there were other Script resources in Service foo, they
would stop in the reverse 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 stop in the reverse order listed in the Service foo portion of
/etc/cluster/cluster.conf.
5. fs:1 — This is a File System resource. If there were other File System resources in Service
foo, they would stop in the reverse order listed in the Service foo portion of
/etc/cluster/cluster.conf.
6. 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.
7. 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.3. Inherit ance, t he <resources> Block, and Reusing Resources
Some resources benefit by inheriting values from a parent resource; that is commonly the case in an
NFS service. Example D.5, “ NFS Service Set Up for Resource Reuse and Inheritance” shows a
typical NFS service configuration, set up for resource reuse and inheritance.
Example D.5. N FS Service Set Up f o r Reso u rce Reu se an d In h erit an ce
<resources>
<nfsclient name="bob" target="bob.example.com" options="rw,no_root_squash"/>
<nfsclient name="jim" target="jim.example.com" options="rw,no_root_squash"/>
<nfsexport name="exports"/>
</resources>
HA Resou rce Behavior
115