From d0dd8df75298da91145a78d4b692551e91331cee Mon Sep 17 00:00:00 2001 From: Ronnie Sahlberg Date: Fri, 7 Sep 2007 12:20:48 +1000 Subject: [PATCH] update web nfs with the new NFS_HOSTNAME variable we need to be able to stat notify using the correct hostname (This used to be ctdb commit 1498e33e48a4654e02b74a00ef7473fed3225d69) --- ctdb/web/nfs.html | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/ctdb/web/nfs.html b/ctdb/web/nfs.html index a732370c2f2..4634e67dcee 100644 --- a/ctdb/web/nfs.html +++ b/ctdb/web/nfs.html @@ -41,14 +41,15 @@ This file should look something like : 
   CTDB_MANAGES_NFS=yes
   NFS_TICKLE_SHARED_DIRECTORY=/gpfs0/nfs-tickles
+  STATD_SHARED_DIRECTORY=/gpfs0/nfs-state
+  NFS_HOSTNAME=ctdb
   STATD_PORT=595
   STATD_OUTGOING_PORT=596
   MOUNTD_PORT=597
   RQUOTAD_PORT=598
   LOCKD_TCPPORT=599
   LOCKD_UDPPORT=599
-  STATD_SHARED_DIRECTORY=/gpfs0/nfs-state
-  STATD_HOSTNAME="ctdb -H /etc/ctdb/statd-callout -p 97"
+  STATD_HOSTNAME="$NFS_HOSTNAME -H /etc/ctdb/statd-callout -p 97"
The CTDB_MANAGES_NFS line tells the events scripts that CTDB is to manage startup and shutdown of the NFS and NFSLOCK services.
@@ -75,6 +76,11 @@ The reason to do this is to improve the speed at which a client will detect that the tcp connection for NFS needs to be reestablished and to speed up recovery in the client.
+NFS_HOSTNAME is the dns name for the ctdb cluster and which is used when clients map nfs shares. This name must be in DNS and resolve back into the public ip addresses of the cluster.
+Always use the same name here as you use for the samba hostname. + + +

chkconfig

Since CTDB will manage and start/stop/restart the nfs and the nfslock services, you must disable them using chkconfig. -- 2.47.3