Installation guide

/etc/cl uster/cl uster.co nf. In addition, non-typed child resources are started after all typed

child resources have started and are stopped before any typed child resources have stopped.

Note

The only resource to implement defined child resource type ordering is the Service resource.

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

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

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

Ordering” .

C.2.1. T yped Child Resource St art and St op 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 that can range 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 C.1, “ Child Resource Type Start and Stop Order” shows the start and stop values for each

resource type; Example C.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 C.1. Ch ild Reso u rce T yp 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

GFS2 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

Examp le C.2. R eso u rce St art an d St o p Valu es: Excerp t f ro m Service R eso u rce Ag en t ,

service. sh

</special>

Red Hat Ent erprise Linux 6 Clust er Administ rat ion

208