rpc.mountd: let mountd consult /etc/services for port

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

diff --git a/utils/statd/statd.man b/utils/statd/statd.man
index 4ddb634041d57abd1609ae23a19a5a1615844269..203f8c97ae2da491c7e9e6d07330e3edebbd5ab7 100644 (file)
--- a/utils/statd/statd.man
+++ b/utils/statd/statd.man
@@ -12,7 +12,7 @@
 .SH NAME
 rpc.statd \- NSM service daemon
 .SH SYNOPSIS
 .SH NAME
 rpc.statd \- NSM service daemon
 .SH SYNOPSIS

-.BI "rpc.statd [-dh?FLNvVw] [-H " prog "] [-n " my-name "] [-o " outgoing-port "] [-p " listener-port "] [-P " path " ]
+.BI "rpc.statd [-dh?FLNvV] [-H " prog "] [-n " my-name "] [-o " outgoing-port "] [-p " listener-port "] [-P " path " ]

 .SH DESCRIPTION
 File locks are not part of persistent file system state.
 Lock state is thus lost when a host reboots.
 .SH DESCRIPTION
 File locks are not part of persistent file system state.
 Lock state is thus lost when a host reboots.


@@ -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,


@@ -221,7 +219,10 @@ for details.
 Specifies the port number used for RPC listener sockets.
 If this option is not specified,
 .B rpc.statd
 Specifies the port number used for RPC listener sockets.
 If this option is not specified,
 .B rpc.statd

-chooses a random ephemeral port for each listener socket.
+will try to consult
+.IR /etc/services ,
+if gets port succeed, set the same port for all listener socket,
+otherwise chooses a random ephemeral port for each listener socket.

 .IP
 This option can be used to fix the port value of its listeners when
 SM_NOTIFY requests must traverse a firewall between clients and servers.
 .IP
 This option can be used to fix the port value of its listeners when
 SM_NOTIFY requests must traverse a firewall between clients and servers.


@@ -274,9 +275,6 @@ listeners using the
 .B tcp_wrapper
 library or
 .BR iptables (8).
 .B tcp_wrapper
 library or
 .BR iptables (8).

-Note that the
-.B tcp_wrapper
-library supports only IPv4 networking.

 To use the
 .B tcp_wrapper
 library, add the hostnames of peers that should be allowed access to
 To use the
 .B tcp_wrapper
 library, add the hostnames of peers that should be allowed access to


@@ -295,7 +293,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


@@ -312,13 +309,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.