Installation guide

D.2.2. Non-t yped Child Resource St art and St op 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” .

Example D.4 . No n - t yp ed an d T yp ed C h ild R eso u rce in a Service

</service>

No n-t ype d Child Reso urce St art ing Orde r

In Example D.4, “ Non-typed and Typed Child Resource in a Service” , the child resources are started

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.

5. script:1 — This is a Script resource. If there were other Script resources in Service foo, they

would start in the order listed in the Service foo portion of /etc/cluster/cluster.conf.

6. nontypedresource:foo — This is a non-typed resource. Because it is a non-typed

resource, it is started after the typed resources start. In addition, its order in the Service

resource is before the other non-typed resource, nontypedresourcetwo:bar; therefore, it

is started before nontypedresourcetwo:bar. (Non-typed resources are started in the order

that they appear in the Service resource.)

7. nontypedresourcetwo:bar — This is a non-typed resource. Because it is a non-typed

resource, it is started after the typed resources start. In addition, its order in the Service

resource is after the other non-typed resource, nontypedresource:foo; therefore, it is

Red Hat Ent erprise Linux 5 Clust er Administ rat ion

114