Hi,
I wrote:
>...
> > I'm confused with the boot script language. It says on the new
> > client page for NFS-Utils to only install and run the bootscripts
> > if you want the *server*, yet on the server page it says the
> > bootscripts are used for *client tools*. Confusing to me.
>
> As I understand that all right, there are two different sets of
> bootscripts. One for the server and one for the client (make
> install-nfs-server vs. make install-nfs-client).
> The client one starts only the rpc.statd daemon. The description of
> rpc.statd says that it "Runs on the NFS server only.". If that is true,
> than there is no need for any bootscript on the client side at all. For me,
> my NFS mount always worked very well (on client side) without any of those
> daemon started. So I think the start of rpc.statd on the client side is not
> sooo important...
Thats a bit nonsense - according to the nfs-howto the rpc.statd must be
started on both sides to enable file locking. When not started on client
side, file locking is not available but everything else works fine. So, seems
so that the client boot script is somewhat optional but highly recommended.
Please have a look to the attached patch on the nfsutils.xml to address most
of Randys points. The "nfsmount" thing is still open. I think this from the
very past and that program doesn't exist anylonger. The question is, what is
start-statd good for and who calls it?
--
Thomas
Index: nfs-utils.xml
===================================================================
--- nfs-utils.xml (Revision 7293)
+++ nfs-utils.xml (Arbeitskopie)
@@ -69,23 +69,25 @@
<bridgehead renderas="sect3">NFS Utilities Dependencies</bridgehead>
<bridgehead renderas="sect4">Required</bridgehead>
- <para role="required"><xref linkend="portmap"/> (Runtime dependency)</para>
+ <para role="required"><xref linkend="tcpwrappers"/>,
+ <xref linkend="portmap"/> (Runtime dependency)</para>
<bridgehead renderas="sect4">Optional for NFSv4 Support</bridgehead>
- <para role="optional"><xref linkend="pkgconfig"/> and
- <ulink url="http://www.monkey.org/~provos/libevent/";>libevent</ulink> and
- <ulink url="http://www.citi.umich.edu/projects/nfsv4/linux/";>libnsfidmap</ulink>
+ <para role="optional"><xref linkend="pkgconfig"/>,
+ <ulink url="http://www.monkey.org/~provos/libevent/";>libevent</ulink>, and
+ <ulink url="http://www.citi.umich.edu/projects/nfsv4/linux/";>libnsfidmap</ulink>
</para>
<bridgehead renderas="sect4">Optional for GSS (RPC Security) Support</bridgehead>
- <para role="optional"><xref linkend="pkgconfig"/>, and
+ <para role="optional"><xref linkend="pkgconfig"/>,
<xref linkend="mitkrb"/> or
<xref linkend="heimdal"/> or
<ulink url="http://www.citi.umich.edu/projects/nfsv4/linux/";>libgssapi</ulink>, and
- <ulink url="http://www.citi.umich.edu/projects/nfsv4/linux/";>librpcsecgss</ulink>;
- for additional SPKM-3 support, install
- <ulink url="http://www.citi.umich.edu/projects/nfsv4/linux/";>SPKM-3</ulink></para>
+ <ulink url="http://www.citi.umich.edu/projects/nfsv4/linux/";>librpcsecgss</ulink></para>
+ <bridgehead renderas="sect4">Optional for SPKM-3 Support</bridgehead>
+ <para><ulink url="http://www.citi.umich.edu/projects/nfsv4/linux/";>SPKM-3</ulink></para>
+
<para condition="html" role="usernotes">User Notes:
<ulink url="&blfs-wiki;/nfs-utils"/></para>
@@ -148,18 +150,16 @@
--disable-gss &&
make</userinput></screen>
+ <para>If your <filename class="directory">/usr</filename> directory
+ is NFS mounted, you should install the executables in
+ <filename class="directory">/sbin</filename> by passing
+ an additional parameter <option>--sbindir=/sbin</option> to the
+ above <command>./configure</command> command.</para>
+
<para>This package does not come with a test suite.</para>
<para>Now, as the <systemitem class="username">root</systemitem> user:</para>
- <note>
- <para>If your <filename class="directory">/usr</filename> directory
- is NFS mounted, you should install the executables in
- <filename class="directory">/sbin</filename> by passing
- an additional parameter <option>--sbindir=/sbin</option> to the
- above <command>./configure</command> command.</para>
- </note>
-
<screen role='root'><userinput>make install</userinput></screen>
</sect2>
@@ -173,9 +173,6 @@
<para><parameter>--disable-gss</parameter>: Disables support for
RPCSEC GSS (RPC Security).</para>
- <para><option>--with-tcp-wrappers</option>: Use this option to enable
- tcpwrappers support.</para>
-
</sect2>
<sect2 role="configuration">
@@ -232,8 +229,8 @@
<sect4 id="nfs-utils-server-wrappers-support">
<title>tcpwrappers Configuration</title>
- <para>If you enabled support for <application>tcpwrappers</application>,
- ensure you have an entry in the <filename>/etc/hosts.allow</filename>
+ <para>If <application>tcpwrappers</application> is installed, ensure
+ you have an entry in the <filename>/etc/hosts.allow</filename>
file for access from the <command>portmap</command> daemon if you have a
restrictive <filename>/etc/hosts.deny</filename> file.</para>
@@ -251,8 +248,8 @@
and <filename class="directory">/usr</filename> partitions, add the
following to the <filename>/etc/fstab</filename>:</para>
-<screen role="root"><userinput><server-name>:/home /home nfs rw,_netdev,rsize=8192,wsize=8192 0 0
-<server-name>:/usr /usr nfs ro,_netdev,rsize=8192 0 0</userinput></screen>
+<screen role="root"><userinput><replaceable><server-name></replaceable>:/home /home nfs rw,_netdev,rsize=8192,wsize=8192 0 0
+<replaceable><server-name></replaceable>:/usr /usr nfs ro,_netdev,rsize=8192 0 0</userinput></screen>
<indexterm zone="nfs-utils nfs-utils-client-config">
<primary sortas="e-etc-fstab">/etc/fstab</primary>
@@ -295,8 +292,8 @@
<segtitle>Installed Directories</segtitle>
<seglistitem>
- <seg>exportfs, nfsstat, rpc.mountd, rpc.nfsd, rpc.statd, rpcdebug,
- showmount, sm-notify, start-statd, mount.nfs and umount.nfs</seg>
+ <seg>exportfs, mount.nfs, mount.nfs4, nfsstat, rpc.mountd, rpc.nfsd, rpc.statd, rpcdebug,
+ showmount, sm-notify, start-statd and umount.nfs as well as umount.nfs4</seg>
<seg>None</seg>
<seg>/var/lib/nfs</seg>
</seglistitem>
@@ -317,6 +314,26 @@
</listitem>
</varlistentry>
+ <varlistentry id="mountnfs">
+ <term><command>mount.nfs</command></term>
+ <listitem>
+ <para>Used to mount a network share using NFS</para>
+ <indexterm zone="nfs-utils mountnfs">
+ <primary sortas="b-mountnfs">mount.nfs</primary>
+ </indexterm>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry id="mountnfs4">
+ <term><command>mount.nfs4</command></term>
+ <listitem>
+ <para>Used to mount a network share using NFSv4</para>
+ <indexterm zone="nfs-utils mountnfs4">
+ <primary sortas="b-mountnfs4">mount.nfs4</primary>
+ </indexterm>
+ </listitem>
+ </varlistentry>
+
<varlistentry id="nfsstat">
<term><command>nfsstat</command></term>
<listitem>
@@ -351,10 +368,8 @@
<varlistentry id="rpcstatd">
<term><command>rpc.statd</command></term>
<listitem>
- <para>is used by the NFS file locking service,
- <command>rpc.lockd</command>, to implement lock recovery when
- the NFS server machine crashes and reboots. Runs on the NFS
- server only.</para>
+ <para>is used by the NFS file locking service. Run on both sides,
+ client as well as server, when you want file locking enabled.</para>
<indexterm zone="nfs-utils rpcstatd">
<primary sortas="b-rpcstatd">rpc.statd</primary>
</indexterm>
@@ -404,6 +419,26 @@
</listitem>
</varlistentry>
+ <varlistentry id="umountnfs">
+ <term><command>umount.nfs</command></term>
+ <listitem>
+ <para>Used to unmount a network share using NFS</para>
+ <indexterm zone="nfs-utils umountnfs">
+ <primary sortas="b-umountnfs">umount.nfs</primary>
+ </indexterm>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry id="umountnfs4">
+ <term><command>umount.nfs4</command></term>
+ <listitem>
+ <para>Used to unmount a network share using NFSv4</para>
+ <indexterm zone="nfs-utils umountnfs4">
+ <primary sortas="b-umountnfs4">umount.nfs4</primary>
+ </indexterm>
+ </listitem>
+ </varlistentry>
+
</variablelist>
</sect2>
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
