# should ctdb manage starting/stopping the ISCSI service
# CTDB_MANAGES_ISCSI=yes
+# should ctdb manage starting/stopping the NFS service
+# CTDB_MANAGES_NFS=yes
+
# you may wish to raise the file descriptor limit for ctdb
# use a ulimit command here. ctdb needs one file descriptor per
This file should look something like :
<pre>
- CTDB_MANAGES_NFS=yes
NFS_TICKLE_SHARED_DIRECTORY=/gpfs0/nfs-tickles
STATD_SHARED_DIRECTORY=/gpfs0/nfs-state
NFS_HOSTNAME=ctdb
</pre>
-The CTDB_MANAGES_NFS line tells the events scripts that CTDB is to manage startup and shutdown of the NFS and NFSLOCK services.<br>
-
-With this set to yes, CTDB will start/stop/restart these services as required.<br><br>
-
You need to make sure that the lock manager runs on the same port on all nodes in the cluster since some clients will have "issues" and take very long to recover if the port suddenly changes.<br>
599 above is only an example. You can run the lock manager on any available port as long as you use the same port on all nodes.<br><br>
RPCNFSDARGS is used to disable support for NFSv4 which is not yet supported by CTDB.
+<h2>/etc/sysconfig/ctdb</h2>
+Add the following line to /etc/sysconfig/ctdb :
+
+<pre>
+ CTDB_MANAGES_NFS=yes
+</pre>
+The CTDB_MANAGES_NFS line tells the events scripts that CTDB is to manage startup and shutdown of the NFS and NFSLOCK services.<br>
+
+With this set to yes, CTDB will start/stop/restart these services as required.<br><br>
+
<h2>chkconfig</h2>