The RHEL 5 bug this is cloned from references NFSv3 servers since that is default in RHEL5.  In RHEL 6 NFSv4 should be used, but we'll need to provide different config information than what is provided below.

+++ This bug was initially created as a clone of Bug #692220 +++

Description of problem:
rgmanager supports making NFSv3 servers highly available in an active/passive manner when backed by a non-clustered filesystem.  In this configuration scenario, you would want to be able to fail over the locks from one server to another so that the passive node can immediately pick up where the failed server left off.

This lock failover has not been extensively tested in a while, so this bug is to track testing of lock failover specifically.

Notes:

> 1) Add this to /etc/sysconfig/nfs:
> 
>    STATDARG="-H /usr/sbin/clunfslock"
> 
> 2) In cluster.conf, your service _MUST_ be structured like this; if you
> don't get the dependency chains just right, it will not work:
> 
>    ...
>    <resources>
>      <nfsexport name="nfsexports"/>
>    </resources>
>    ...
>    <service name="foo" nfslock="1" ... >
>      <fs name="fs1" ... >
>        <nfsexport ref="nfsexports">
>          <nfsclient ... />
>          <nfsclient ... />
>          ...
>        </nfsexport>
>      </fs>
>      <fs name="fs2" ... >
>        <nfsexport ref="nfsexports">
>          <nfsclient ... />
>          <nfsclient ... />
>          ...
>        </nfsexport>
>      </fs>
>      <ip ... />
>    </service>