Linux-NFS Archive on lore.kernel.org
 help / color / Atom feed
From: Marcos Paulo de Souza <marcos.souza.org@gmail.com>
To: linux-nfs@vger.kernel.org, steved@redhat.com
Cc: Marcos Paulo de Souza <mpdesouza@suse.com>
Subject: [PATCH] utils/statd.man: Clarify the --name argument usage
Date: Tue,  1 Oct 2019 21:52:41 -0300
Message-ID: <20191002005241.28308-1-marcos.souza.org@gmail.com> (raw)

From: Marcos Paulo de Souza <mpdesouza@suse.com>

The man page does not clarifies that the --name argument is only used by
the sm-notify command, and statd itself listen to all interfaces. This
change makes clear that the --name argument is only passed to sm-notify.

Signed-off-by: Marcos Paulo de Souza <mpdesouza@suse.com>
---
 utils/statd/statd.man | 10 ++++------
 1 file changed, 4 insertions(+), 6 deletions(-)

diff --git a/utils/statd/statd.man b/utils/statd/statd.man
index 71d58461..03732a6f 100644
--- a/utils/statd/statd.man
+++ b/utils/statd/statd.man
@@ -185,18 +185,16 @@ restarts without the
 option.
 .TP
 .BI "\-n, " "" "\-\-name " ipaddr " | " hostname
-Specifies the bind address used for RPC listener sockets.
+This string is only used by the
+.B sm-notify
+command as the source address from which to send reboot notification requests.
+.IP
 The
 .I ipaddr
 form can be expressed as either an IPv4 or an IPv6 presentation address.
 If this option is not specified,
 .B rpc.statd
 uses a wildcard address as the transport bind address.
-.IP
-This string is also passed to the
-.B sm-notify
-command to be used as the source address from which
-to send reboot notification requests.
 See
 .BR sm-notify (8)
 for details.
-- 
2.23.0


             reply index

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-02  0:52 Marcos Paulo de Souza [this message]
2019-10-10 14:57 ` Marcos Paulo de Souza
2019-10-14 18:19 ` Steve Dickson

Reply instructions:

You may reply publically to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20191002005241.28308-1-marcos.souza.org@gmail.com \
    --to=marcos.souza.org@gmail.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=mpdesouza@suse.com \
    --cc=steved@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Linux-NFS Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-nfs/0 linux-nfs/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-nfs linux-nfs/ https://lore.kernel.org/linux-nfs \
		linux-nfs@vger.kernel.org
	public-inbox-index linux-nfs

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-nfs


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git