Installation guide

For more information about typed child resource start and stop ordering, refer to Section D.2.1,

“ Typed Child Resource Start and Stop Ordering” . For more information about non-typed child

resource start and stop ordering, refer to Section D.2.2, “ Non-typed Child Resource Start and Stop

Ordering” .

D.2.1. T yped Child Resource Start and Stop Ordering

For a typed child resource, the type attribute for the child resource defines the start order and the stop

order of each resource type with a number ranging from 1 to 100; one value for start, and one value

for stop. The lower the number, the earlier a resource type starts or stops. For example, Table D.1,

“ Child Resource Type Start and Stop Order” shows the start and stop values for each resource type;

Example D.2, “ Resource Start and Stop Values: Excerpt from Service Resource Agent, service.sh”

shows the start and stop values as they appear in the Service resource agent, service.sh. For the

Service resource, all LVM children are started first, followed by all File System children, followed by

all Script children, and so forth.

T ab le D.1. Ch ild Reso u rce Typ e St art an d St o p O rd er

Reso u rce Ch ild T yp e St art - o rd er Valu e St o p - o rd er Valu e

LVM lvm 1 9

File System fs 2 8

GFS File System clusterfs 3 7

NFS Mount netfs 4 6

NFS Export nfsexport 5 5

NFS Client nfsclient 6 4

IP Address ip 7 2

Samba smb 8 3

Script script 9 1

Example D.2. R eso u rce St art an d St o p Valu es: Excerp t f ro m Service Reso u rce Agen t ,

service.sh

</special>

Ordering within a resource type is preserved as it exists in the cluster configuration file,

/etc/cluster/cluster.conf. For example, consider the starting order and stopping order of the

typed child resources in Example D.3, “ Ordering Within a Resource Type” .

Example D.3. O rd erin g Wit h in a Reso u rce Typ e

Red Hat Ent erprise Linux 5 Clust er Administ rat ion

112