From: "Steinar H. Gunderson" <sesse@debian.org>
To: nfs@lists.sourceforge.net
Subject: [PATCH] Clarify language in man exportfs
Date: Mon, 29 Oct 2007 19:04:43 +0100 [thread overview]
Message-ID: <20071029180443.GA6109@uio.no> (raw)
(I still have two pending minor patches, by the way :-) )
As discussed in a user case earlier, the wording in the exportfs man page can
be a bit confusing, implying that "exportfs -u :/foo" will unexport /foo from
all hosts, which it won't. Thus, make the language clearer -- based on
suggestion/patch from David Liontooth.
Signed-off-by: Steinar H. Gunderson <sesse@debian.org>
--- nfs-utils-1.1.1.orig/utils/exportfs/exportfs.man
+++ nfs-utils-1.1.1/utils/exportfs/exportfs.man
@@ -167,11 +167,13 @@ all entries listed in
are removed from the kernel export tables, and the file is cleared. This
effectively shuts down all NFS activity.
.P
-To remove individual export entries, one can specify a
+To remove an export to a host, specify a
.I host:/path
pair. This deletes the specified entry from
.B xtab
and removes the corresponding kernel entry (if any).
+To remove one or more exports to several hosts, use
+.BR "exportfs -ua" .
.P
.\" -------------------- Dumping the Export Table -----------------
.SS Dumping the Export Table
/* Steinar */
--
Homepage: http://www.sesse.net/
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next reply other threads:[~2007-10-29 18:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-29 18:04 Steinar H. Gunderson [this message]
2007-11-03 13:18 ` [PATCH] Clarify language in man exportfs Steve Dickson
Reply instructions:
You may reply publicly 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=20071029180443.GA6109@uio.no \
--to=sesse@debian.org \
--cc=nfs@lists.sourceforge.net \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox