diff options
| author | Chuck Lever <chuck.lever@oracle.com> | 2010-03-17 06:15:08 -0400 |
|---|---|---|
| committer | Steve Dickson <steved@redhat.com> | 2010-03-17 06:15:08 -0400 |
| commit | 900df0e7c0b9006d72d8459b30dc2cd69ce495a5 (patch) | |
| tree | ea8d4ef6424853844a1b5931aea20d3cabb8235b /utils/statd/statd.man | |
| parent | 70c59e231e7257ac93b68ba4b844f8d10a6af4a8 (diff) | |
| download | nfs-utils-900df0e7c0b9006d72d8459b30dc2cd69ce495a5.tar.gz nfs-utils-900df0e7c0b9006d72d8459b30dc2cd69ce495a5.tar.xz nfs-utils-900df0e7c0b9006d72d8459b30dc2cd69ce495a5.zip | |
sm-notify: Use my_name when sending SM_NOTIFY requests
The mon_name argument of an SM_NOTIFY request is a string that
identifies the rebooting host.
sm-notify should send the my_name provided by the local lockd at the
time the remote was monitored, rather than cocking up a mon_name
argument based on the present return value of gethostname(3). If the
local system's hostname happened to change after the last reboot, then
the string returned by gethostname(3) will not be recognized by the
remote. Thus the remote will never initiate lock recovery for the
original named host, possibly leaving stale locks.
The existing behavior of using the -v command line option as the
mon_name argument is preserved, but we now prevent sending an IP
presentation address, as some non-Linux implementations don't
recognize addresses as valid mon_names.
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
Reviewed-by: Jeff Layton <jlayton@redhat.com>
Signed-off-by: Steve Dickson <steved@redhat.com>
Diffstat (limited to 'utils/statd/statd.man')
| -rw-r--r-- | utils/statd/statd.man | 14 |
1 files changed, 2 insertions, 12 deletions
diff --git a/utils/statd/statd.man b/utils/statd/statd.man index ffc5e95..ca00e24 100644 --- a/utils/statd/statd.man +++ b/utils/statd/statd.man @@ -100,11 +100,9 @@ It uses the string as the destination. To identify which host has rebooted, the .B sm-notify -command normally sends the results of -.BR gethostname (3) -as the +command sends the .I my_name -string. +string recorded when that remote was monitored. The remote .B rpc.statd matches incoming SM_NOTIFY requests using this string, @@ -292,7 +290,6 @@ man pages. .SH ADDITIONAL NOTES Lock recovery after a reboot is critical to maintaining data integrity and preventing unnecessary application hangs. -.PP To help .B rpc.statd match SM_NOTIFY requests to NLM requests, a number of best practices @@ -309,13 +306,6 @@ consistent The hostname the client uses to mount the server should match the server's .I mon_name in SM_NOTIFY requests it sends -.IP -The use of network addresses as a -.I mon_name -or a -.I my_name -string should be avoided when -interoperating with non-Linux NFS implementations. .PP Unmounting an NFS file system does not necessarily stop either the NFS client or server from monitoring each other. |