sm-notify: Use my_name when sending SM_NOTIFY requests

[nfs-utils.git] / utils / statd / statd.man

diff --git a/utils/statd/statd.man b/utils/statd/statd.man
index ffc5e950990c5f7f0b7c1c0b9d06199aed030a41..ca00e24af6ede8cc68aca9c17aea27528aea54d2 100644 (file)
--- 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
 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
 .I my_name

-string.
+string recorded when that remote was monitored.

 The remote
 .B rpc.statd
 matches incoming SM_NOTIFY requests using this string,
 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.
 .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
 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
 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.
 .PP
 Unmounting an NFS file system does not necessarily stop
 either the NFS client or server from monitoring each other.