diff options
| author | Ronnie Sahlberg <sahlberg@ronnie> | 2007-07-10 12:43:46 +1000 |
|---|---|---|
| committer | Ronnie Sahlberg <sahlberg@ronnie> | 2007-07-10 12:43:46 +1000 |
| commit | 26fc2ebd4bfafc9f2875fbb87ade7d1d96138d70 (patch) | |
| tree | 5bb0c247273324b84cc0445fcc7ed390278aa4cb /ctdb/web | |
| parent | d81bca20729759e357ed61781454b601fdb58686 (diff) | |
| download | samba-26fc2ebd4bfafc9f2875fbb87ade7d1d96138d70.tar.gz samba-26fc2ebd4bfafc9f2875fbb87ade7d1d96138d70.tar.xz samba-26fc2ebd4bfafc9f2875fbb87ade7d1d96138d70.zip | |
update the documentation for NFS to mention that the lock manager must
run on the same port on all nodes.
remove the CTDB_MANAGES_NFSLOCK variable that is no longer used
(This used to be ctdb commit 389a503c44c999e46caa344c4bc073336e797909)
Diffstat (limited to 'ctdb/web')
| -rw-r--r-- | ctdb/web/nfs.html | 10 |
1 files changed, 6 insertions, 4 deletions
diff --git a/ctdb/web/nfs.html b/ctdb/web/nfs.html index caff4001f8a..6bec33bc648 100644 --- a/ctdb/web/nfs.html +++ b/ctdb/web/nfs.html @@ -47,16 +47,18 @@ which causes problems on some clients.<br> This file should look something like : <pre> CTDB_MANAGES_NFS=yes - CTDB_MANAGES_NFSLOCK=yes + LOCKD_TCPPORT=599 + LOCKD_UDPPORT=599 STATD_SHARED_DIRECTORY=/gpfs0/nfs-state - STATD_HOSTNAME=\"ctdb -P $STATD_SHARED_DIRECTORY/192.168.1.1 -H /etc/ctdb/statd-callout -p 97\" + STATD_HOSTNAME="ctdb -P $STATD_SHARED_DIRECTORY/192.168.1.1 -H /etc/ctdb/statd-callout -p 97" </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> -The CTDB_MANAGES_NFSLOCK line tells the events scripts that CTDB is also to manage the nfs lock manager.<br> +With this set to yes, CTDB will start/stop/restart these services as required.<br><br> -With these 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> STATD_SHARED_DIRECTORY is the shared directory where statd and the statd-callout script expects that the state variables and lists of clients to notify are found.<br> |