| 
Typed Child Resource Start and Stop Ordering97NoteThe only resource to implement defined child resource type ordering is the Serviceresource.For more information about typed child resource start and stop ordering, refer to Section D.2.1, “TypedChild Resource Start and Stop Ordering”. For more information about non-typed child resource startand stop ordering, refer to Section D.2.2, “Non-typed Child Resource Start and Stop Ordering”.D.2.1. Typed Child Resource Start and Stop OrderingFor a typed child resource, the type attribute for the child resource defines the start order and thestop order of each resource type with a number from 1 and 100; one value for start, and one valuefor 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 theService resource, all LVM children are started first, followed by all File System children, followed by allScript children, and so forth.Resource Child Type Start-order Value Stop-order ValueLVM lvm 1 9File System fs 2 8GFS File System clusterfs 3 7NFS Mount netfs 4 6NFS Export nfsexport 5 5NFS Client nfsclient 6 4IP Address ip 7 2Samba smb 8 3Script script 9 1Table D.1. Child Resource Type Start and Stop Order tag="rgmanager"> root="1" maxinstances="1"/> type="lvm" start="1" stop="9"/> type="fs" start="2" stop="8"/> type="clusterfs" start="3" stop="7"/> type="netfs" start="4" stop="6"/> type="nfsexport" start="5" stop="5"/> type="nfsclient" start="6" stop="4"/> type="ip" start="7" stop="2"/> type="smb" start="8" stop="3"/> type="script" start="9" stop="1"/>Example D.2. Resource Start and Stop Values: Excerpt from Service Resource Agent, service.sh |
