docs/180955: Update to Network-NFS Documentation
Ken Reed
kreed002 at gmail.com
Tue Jul 30 20:40:00 UTC 2013
>Number: 180955
>Category: docs
>Synopsis: Update to Network-NFS Documentation
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: freebsd-doc
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: update
>Submitter-Id: current-users
>Arrival-Date: Tue Jul 30 20:40:00 UTC 2013
>Closed-Date:
>Last-Modified:
>Originator: Ken Reed
>Release: 9.1-Release-p5
>Organization:
>Environment:
FreeBSD chaos 9.1-RELEASE-p5 FreeBSD 9.1-RELEASE-p5 #0: Sat Jul 27 01:14:23 UTC 2013 root at amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64
>Description:
Updating NFS doc to use services instead of specific binaries. Also offered a couple of minor points of clarification in the text.
>How-To-Repeat:
>Fix:
Patch attached with submission follows:
Index: en_US.ISO8859-1/books/handbook/network-servers/chapter.xml
===================================================================
--- en_US.ISO8859-1/books/handbook/network-servers/chapter.xml (revision 42478)
+++ en_US.ISO8859-1/books/handbook/network-servers/chapter.xml (working copy)
@@ -267,7 +267,7 @@
</sect2>
<sect2 id="network-inetd-conf">
- <!-- XXX This section isn't very clear, and could do with some lovin' -->
+ <!-- XXX This section is not very clear and could do with some tlc -->
<title><filename>inetd.conf</filename></title>
<para>Configuration of <application>inetd</application> is
@@ -819,20 +819,15 @@
<para>Please refer to <xref linkend="configtuning-rcd"/> for
more information about using rc scripts.</para>
- <para>Alternatively, a reboot will make FreeBSD set everything
- up properly. A reboot is not necessary though.
- Executing the following commands as <username>root</username>
- should start everything up.</para>
+ <para>NFS services can now be started by running the following
+ command, on the <acronym>NFS</acronym> server, as
+ <username>root</username>:</para>
- <para>On the <acronym>NFS</acronym> server:</para>
+ <screen>&prompt.root; <userinput>service nfsd start</userinput></screen>
- <screen>&prompt.root; <userinput>rpcbind</userinput>
-&prompt.root; <userinput>nfsd -u -t -n 4</userinput>
-&prompt.root; <userinput>mountd -r</userinput></screen>
-
<para>On the <acronym>NFS</acronym> client:</para>
- <screen>&prompt.root; <userinput>nfsiod -n 4</userinput></screen>
+ <screen>&prompt.root; <userinput>service nfsclient restart</userinput></screen>
<para>Now everything should be ready to actually mount a remote
file system. In these examples the server's name will be
@@ -1609,7 +1604,7 @@
good reason, never propagate passwords for
<username>root</username> and other administrative
accounts to all the servers in the NIS domain. Therefore,
- before the the NIS maps are initialized, configure the
+ before the NIS maps are initialized, configure the
primary password files:</para>
<screen>&prompt.root; <userinput>cp /etc/master.passwd /var/yp/master.passwd</userinput>
@@ -1649,7 +1644,7 @@
Questions will all be asked at the beginning of the procedure.
Do you want this procedure to quit on non-fatal errors? [y/n: n] <userinput>n</userinput>
Ok, please remember to go back and redo manually whatever fails.
-If you don't, something might not work.
+If not, something might not work.
At this point, we have to construct a list of this domains YP servers.
rod.darktech.org is already known as master server.
Please continue to add any slave servers, one per line. When you are
@@ -1711,7 +1706,7 @@
Do you want this procedure to quit on non-fatal errors? [y/n: n] <userinput>n</userinput>
Ok, please remember to go back and redo manually whatever fails.
-If you don't, something might not work.
+If not, something might not work.
There will be no further questions. The remainder of the procedure
should take a few minutes, to copy the databases from ellington.
Transferring netgroup...
@@ -1756,7 +1751,7 @@
ypxfr: Exiting: Map successfully transferred
coltrane has been setup as an YP slave server without any errors.
-Don't forget to update map ypservers on ellington.</screen>
+Remember to update map ypservers on ellington.</screen>
<para>There should be a directory called
<filename>/var/yp/test-domain</filename>. Copies of the
>Release-Note:
>Audit-Trail:
>Unformatted:
More information about the freebsd-doc
mailing list