os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Update rpcbind/portmap usage in the NFS and NIS sections to match at

Browse source 
first 5.X
While I'm there, add some index references for rpcbind

Based on PR:		docs/75515
Submitted by:		Joel Dahl <joel@automatvapen.se>
This commit is contained in:
Marc Fonvieille 2004-12-26 17:44:20 +00:00
parent f6a2f2ff3f
commit 2cff2d215d
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=23347
1 changed files with 20 additions and 12 deletions

32
en_US.ISO8859-1/books/handbook/network-servers/chapter.sgml
View file

@ -609,12 +609,12 @@ server-program-arguments</programlisting>
order for this to function properly a few processes have to be
configured and running.</para>
<note><para>In &os; 5.X, the <application>portmap</application>
utility has been replaced with the
<application>rpcbind</application> utility. Thus, in &os; 5.X
<note><para>Under &os;&nbsp;4.X, the <application>portmap</application>
utility is used in place of the
<application>rpcbind</application> utility. Thus, in &os;&nbsp;4.X
the user is required to replace every instance of
<application>portmap</application> with
<application>rpcbind</application> in the forthcoming
<application>rpcbind</application> with
<application>portmap</application> in the forthcoming
examples.</para></note>
<para>The server has to be running the following daemons:</para>
@ -627,6 +627,9 @@ server-program-arguments</programlisting>
<secondary>unix clients</secondary>
</indexterm>
<indexterm>
<primary><application>rpcbind</application></primary>
</indexterm>
<indexterm>
<primary><application>portmap</application></primary>
</indexterm>
@ -661,8 +664,8 @@ server-program-arguments</programlisting>
the requests that &man.nfsd.8; passes on to it.</entry>
</row>
<row>
<entry><application>portmap</application></entry>
<entry> The portmapper daemon allows
<entry><application>rpcbind</application></entry>
<entry> This daemon allows
<acronym>NFS</acronym> clients to discover which port
the <acronym>NFS</acronym> server is using.</entry>
</row>
@ -696,7 +699,7 @@ server-program-arguments</programlisting>
following options are configured in the
<filename>/etc/rc.conf</filename> file:</para>
<programlisting>portmap_enable="YES"
<programlisting>rpcbind_enable="YES"
nfs_server_enable="YES"
mountd_flags="-r"</programlisting>
@ -821,7 +824,7 @@ mountd_flags="-r"</programlisting>
<para>On the <acronym>NFS</acronym> server:</para>
<screen>&prompt.root; <userinput>portmap</userinput>
<screen>&prompt.root; <userinput>rpcbind</userinput>
&prompt.root; <userinput>nfsd -u -t -n 4</userinput>
&prompt.root; <userinput>mountd -r</userinput></screen>
@ -1179,6 +1182,9 @@ Exports list on foobar:
implement NIS on FreeBSD, whether you are trying to create an
NIS server or act as an NIS client:</para>
<indexterm>
<primary><application>rpcbind</application></primary>
</indexterm>
<indexterm>
<primary><application>portmap</application></primary>
</indexterm>
@ -1205,14 +1211,16 @@ Exports list on foobar:
<acronym>DNS</acronym>.</entry>
</row>
<row>
<entry><application>portmap</application></entry>
<entry><application>rpcbind</application></entry>
<entry>Must be running in order to enable
<acronym>RPC</acronym> (Remote Procedure Call, a
network protocol used by NIS). If
<application>portmap</application> is not running, it
<application>rpcbind</application> is not running, it
will be impossible to run an NIS server, or to act as
an NIS client.</entry>
an NIS client (Under &os;&nbsp;4.X
<application>portmap</application> is used in place of
<application>rpcbind</application>).
</row>
<row>
<entry><application>ypbind</application></entry>