source: networking/netprogs/nfs-utils.xml

trunk
Last change on this file was 133eab2, checked in by Bruce Dubbs <bdubbs@…>, 2 months ago

Initial LFS 12.1 tags
  • Property mode set to 100644
File size: 24.4 KB
Line 
1<?xml version="1.0" encoding="UTF-8"?>
2<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
3 "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
4 <!ENTITY % general-entities SYSTEM "../../general.ent">
5 %general-entities;
6
7 <!ENTITY nfs-utils-root "&kernel-dl;/linux/utils/nfs-utils" >
8 <!ENTITY nfs-utils-download-http "&nfs-utils-root;/&nfs-utils-version;/nfs-utils-&nfs-utils-version;.tar.xz">
9 <!ENTITY nfs-utils-download-ftp " ">
10 <!ENTITY nfs-utils-md5sum "907f95977ccf7a522ee32af1534f0e4c">
11 <!ENTITY nfs-utils-size "712 KB">
12 <!ENTITY nfs-utils-buildsize "18 MB (with tests)">
13 <!ENTITY nfs-utils-time "0.2 SBU (with tests)">
14]>
15
16<sect1 id="nfs-utils" xreflabel="nfs-utils-&nfs-utils-version;">
17 <?dbhtml filename="nfs-utils.html"?>
18
19
20 <title>NFS-Utils-&nfs-utils-version;</title>
21
22 <indexterm zone="nfs-utils">
23 <primary sortas="a-Nfs-utils">NFS Utilities</primary>
24 </indexterm>
25
26 <sect2 role="package">
27 <title>Introduction to NFS Utilities</title>
28
29 <para>
30 The <application>NFS Utilities</application> package contains the
31 userspace server and client tools necessary to use the kernel's NFS
32 abilities. NFS is a protocol that allows sharing file systems over the
33 network.
34 </para>
35
36 &lfs121_checked;
37
38 <bridgehead renderas="sect3">Package Information</bridgehead>
39 <itemizedlist spacing='compact'>
40 <listitem>
41 <para>
42 Download (HTTP): <ulink url="&nfs-utils-download-http;"/>
43 </para>
44 </listitem>
45 <listitem>
46 <para>
47 Download (FTP): <ulink url="&nfs-utils-download-ftp;"/>
48 </para>
49 </listitem>
50 <listitem>
51 <para>
52 Download MD5 sum: &nfs-utils-md5sum;
53 </para>
54 </listitem>
55 <listitem>
56 <para>
57 Download size: &nfs-utils-size;
58 </para>
59 </listitem>
60 <listitem>
61 <para>
62 Estimated disk space required: &nfs-utils-buildsize;
63 </para>
64 </listitem>
65 <listitem>
66 <para>
67 Estimated build time: &nfs-utils-time;
68 </para>
69 </listitem>
70 </itemizedlist>
71
72 <bridgehead renderas="sect3">NFS Utilities Dependencies</bridgehead>
73
74 <bridgehead renderas="sect4">Required</bridgehead>
75 <para role="required">
76 <xref linkend="libtirpc"/>,
77 <xref linkend="libevent"/>,
78 <xref linkend="rpcsvc-proto"/>, and
79 <xref linkend="sqlite"/>
80 </para>
81
82 <bridgehead renderas="sect4">Optional</bridgehead>
83 <para role="optional">
84 <xref linkend="cyrus-sasl"/> (for SASL authentication),
85 <xref linkend="lvm2"/> (libdevmapper for NFSv4 support),
86 <!--<xref linkend="libnfsidmap"/> (for NFSv4 support),
87 This is now built in, as of 2.2.1-->
88 <xref linkend="libnsl"/> (for NIS client support),
89 <xref linkend="openldap"/> (for LDAP authentication),
90 <xref linkend="mitkrb"/> or
91 <ulink url="http://www.citi.umich.edu/projects/nfsv4/linux/">
92 libgssapi
93 </ulink>, and
94 <ulink url="http://www.citi.umich.edu/projects/nfsv4/linux/">
95 librpcsecgss
96 </ulink> (for GSS and RPC security support), and
97 <xref linkend="libcap-pam"/>
98 </para>
99
100 <bridgehead renderas="sect4">Required (runtime)</bridgehead>
101 <para role="required">
102 <xref role="runtime" linkend="rpcbind"/>
103 </para>
104
105<!-- NSS configuration isn't directly related to NFS, but left here in case
106 <bridgehead renderas="sect4">Optional (runtime for NIS clients)</bridgehead>
107 <para role="optional">
108 <ulink url="https://github.com/thkukuk/libnss_compat">libnss_compat</ulink>,
109 <ulink url="https://github.com/thkukuk/libnss_nis">libnss_nis</ulink>, and
110 <ulink url="https://github.com/thkukuk/libnss_nisplus">libnss_nisplus</ulink>
111 </para>
112-->
113
114 </sect2>
115
116 <sect2 role="kernel" id='nfs-utils-kernel'>
117 <title>Kernel Configuration</title>
118
119 <para>
120 Enable the following options in the kernel configuration
121 (choose client and/or server support as appropriate) and recompile the
122 kernel if necessary:
123 </para>
124
125 <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
126 href="nfs-utils-kernel.xml"/>
127
128 <para>
129 Select the appropriate sub-options that appear when the above options
130 are selected.
131 </para>
132
133 <note>
134 <para>
135 In BLFS we assume that nfs v3 will be used. If the
136 <emphasis>server</emphasis> offers nfs v4 (for linux, CONFIG_NFSD_V4)
137 then auto-negotiation for v3 will fail and you will need to add
138 <literal>nfsver=3</literal> to the mount options. This also applies
139 if that option is enabled in the <emphasis>client's</emphasis> kernel,
140 for example in a distro trying to mount from a BLFS v3 server.
141 </para>
142 <para>
143 Even if neither end of the connection supports nfs v4, adding
144 <literal>nfsver=3</literal> is still beneficial because it prevents an
145 error message "NFS: bad mount option value specified: minorversion=1"
146 being logged on every mount.
147 </para>
148 </note>
149
150 <indexterm zone="nfs-utils nfs-utils-kernel">
151 <primary sortas="d-nfs-utils">NFS Utilities</primary>
152 </indexterm>
153
154 </sect2>
155
156 <sect2 role="installation" id='nfs-utils-install'
157 xreflabel='NFS Utilities Installation'>
158 <title>Installation of NFS Utilities</title>
159<!--
160 <para>
161 Before you compile the program, ensure that the <systemitem
162 class="username">nobody</systemitem> user and <systemitem
163 class="groupname">nogroup</systemitem> group have been created as done in
164 the current LFS book. You can add them by running the following commands
165 as the <systemitem class="username">root</systemitem> user:
166 </para>
167
168<screen role="nodump"><userinput>groupadd -g 99 nogroup &amp;&amp;
169useradd -c "Unprivileged Nobody" -d /dev/null -g nogroup \
170 -s /bin/false -u 99 nobody</userinput></screen>
171
172 <note>
173 <para>
174 The classic uid and gid values are 65534 which is also -2 when
175 interpreted as a signed 16-bit number. These values impact other files
176 on some filesystems that do not have support for sparse files. The
177 <systemitem class="username">nobody</systemitem> and <systemitem
178 class="groupname">nogroup</systemitem> values are relatively arbitrary.
179 The impact on a server is nil if the <filename>exports</filename> file
180 is configured correctly. If it is misconfigured, an
181 <command>ls -l</command> or <command>ps</command> listing will show a
182 uid or gid number of 65534 instead of a name. The client uses
183 <systemitem class="username">nobody</systemitem> only as the user
184 running <command>rpc.statd</command>.
185 </para>
186 </note>
187-->
188 <para>
189 Install <application>NFS Utilities</application> by running
190 the following commands:
191 </para>
192
193<screen><userinput>./configure --prefix=/usr \
194 --sysconfdir=/etc \
195 --sbindir=/usr/sbin \
196 --disable-nfsv4 \
197 --disable-gss \
198 LIBS="-lsqlite3 -levent_core" &amp;&amp;
199make</userinput></screen>
200
201 <!-- Test breakage: see
202 http://lists.linuxfromscratch.org/pipermail/blfs-book/2017-December/071861.html
203 <para>
204 This package does not come with a working test suite.
205 </para>
206 -->
207
208 <para>
209 Now, as the &root; user:
210 </para>
211
212<!-- dev note: make statduser=$(whoami) DESTDIR=<DESTDIR> install -->
213
214<screen role='root'><userinput>make install &amp;&amp;
215chmod u+w,go+r /usr/sbin/mount.nfs &amp;&amp;
216chown nobody:nogroup /var/lib/nfs</userinput></screen>
217
218 <para>
219 The tests for this package require that the package be installed.
220 In addition, the rpc.statd daemon must not be running and the tests
221 need to be run as the &root; user.
222 </para>
223
224 <para>
225 To test the results, issue, as &root;:
226 </para>
227
228<screen role="root" remap="test"><userinput>make check</userinput></screen>
229
230 </sect2>
231
232 <sect2 role="commands">
233 <title>Command Explanations</title>
234<!--
235 <para>
236 <command>sed ... support/nsm/rpc.c</command>: This sed it required
237 to fix a build issue with glibc-2.26 and later.
238 </para>
239
240 <para>
241 <parameter>- -disable-nfsv4</parameter>: This allows the package to be
242 built when libnfsidmap has not been installed.
243 </para>
244 nfs-utils now carries libnfsidmap
245-->
246 <para>
247 <parameter>--disable-gss</parameter>: Disables support for
248 RPCSEC GSS (RPC Security).
249 </para>
250
251 <para>
252 <parameter>LIBS="-lsqlite3 -levent_core"</parameter>: is required for
253 the fsidd program.
254 </para>
255
256 <para>
257 <command>chown nobody:nogroup /var/lib/nfs</command>: The
258 rpc.statd program uses the ownership of this directory to set
259 it's UID and GID. This command sets those to unprivileged entries.
260 </para>
261
262 </sect2>
263
264 <sect2 role="configuration">
265 <title>Configuring NFS Utilities</title>
266
267 <sect3 id='nfs-utils-server-config'>
268 <title>Server Configuration</title>
269
270 <para>
271 <filename>/etc/exports</filename> contains the exported directories
272 on NFS servers. Refer to the <filename>exports.5</filename> manual page
273 for the syntax of this file. Also refer to the "NFS HowTo" available at
274 <ulink url="https://nfs.sourceforge.net/nfs-howto/"/> for information on
275 how to configure the servers and clients in a secure manner. For
276 example, for sharing the <filename class="directory">/home</filename>
277 directory over the local network, the following line may be added:
278 </para>
279
280<screen role="nodump"><userinput>cat &gt;&gt; /etc/exports &lt;&lt; EOF
281<replaceable>/home 192.168.0.0/24</replaceable>(rw,subtree_check,anonuid=99,anongid=99)
282EOF</userinput></screen>
283
284 <note>
285 <para>
286 Be sure to replace the directory, network address. and prefix above
287 to match your network. The only space in the line above should be
288 between the directory and the network address.
289 </para>
290 </note>
291
292 <indexterm zone="nfs-utils nfs-utils-server-config">
293 <primary sortas="e-etc-exportfs">/etc/exportfs</primary>
294 </indexterm>
295
296 <sect4 id="nfs-utils-server-init">
297 <title><phrase revision="sysv">Boot Script</phrase>
298 <phrase revision="systemd">Systemd Units</phrase></title>
299
300 <para>
301 Install the
302 <phrase revision="sysv">
303 <filename>/etc/rc.d/init.d/nfs-server</filename>
304 init script
305 </phrase>
306 <phrase revision="systemd">NFSv4 server units</phrase>
307 included in the <xref linkend="bootscripts" revision="sysv"/>
308 <xref linkend="systemd-units" revision="systemd"/> package
309 to start the server at boot.
310 </para>
311
312<screen role="root" revision="systemd"><userinput>make install-nfsv4-server</userinput></screen>
313
314 <para revision="systemd">
315 If you have disabled NFSv4 support, run the following command as the
316 <systemitem class="username">root</systemitem> user to omit the NFSv4
317 specific systemd units:
318 </para>
319
320<!-- both -->
321<screen role="root"><userinput>make install-nfs-server</userinput></screen>
322
323 <indexterm zone="nfs-utils nfs-utils-server-init" revision="sysv">
324 <primary sortas="f-nfs-server">nfs-server</primary>
325 </indexterm>
326
327 <para revision="sysv">
328 Now create the
329 <filename>/etc/sysconfig/nfs-server</filename> configuration file:
330 </para>
331
332<screen role="root" revision="sysv"><userinput>cat &gt; /etc/sysconfig/nfs-server &lt;&lt; "EOF"
333<literal>PORT="2049"
334PROCESSES="8"
335KILLDELAY="10"</literal>
336EOF</userinput></screen>
337
338 <note revision="sysv">
339 <para>
340 The above parameters may be optionally placed in
341 <filename>/etc/sysconfig/rc.site</filename>.
342 </para>
343 </note>
344
345 <indexterm zone="nfs-utils nfs-utils-server-init" revision="sysv">
346 <primary
347 sortas="e-etc-sysconfig-nfs-server">/etc/sysconfig/nfs-server</primary>
348 </indexterm>
349
350 <para revision="systemd">
351 You can edit the <filename>/etc/default/nfs-utils</filename>
352 file to change the startup options for NFS daemons. Defaults
353 should be fine for most use cases.
354 </para>
355
356 <indexterm zone="nfs-utils nfs-utils-server-init" revision="systemd">
357 <primary sortas="e-etc-default-nfs-utils">/etc/default/nfs-utils</primary>
358 </indexterm>
359
360 </sect4>
361
362 </sect3>
363
364 <sect3 id='nfs-utils-client-config'>
365 <title>Client Configuration</title>
366
367 <para>
368 <filename>/etc/fstab</filename> contains the directories that
369 are to be mounted on the client. Alternately the partitions can be
370 mounted by using the <command>mount</command> command with the proper
371 options. To mount the <filename class="directory">/home</filename>
372 and <filename class="directory">/usr</filename> partitions, add the
373 following to the <filename>/etc/fstab</filename>:
374 </para>
375
376<screen role="nodump"><userinput><replaceable>&lt;server-name&gt;</replaceable>:/home /home nfs rw,_netdev 0 0
377<replaceable>&lt;server-name&gt;</replaceable>:/usr /usr nfs ro,_netdev 0 0</userinput></screen>
378
379 <para>
380 The options which can be used are specified in <command>man 5 nfs
381 </command>. If both the client and server are running recent versions
382 of linux, most of the options will be negotiated (but see the Note
383 above on nfsver=3). You can specify either <literal>rw</literal> or
384 <literal>ro</literal>, <literal>_netdev</literal> if the filesystem is
385 to be automatically mounted at boot, or <literal>noauto</literal> (and
386 perhaps <literal>user</literal>) for other filesystems.
387 </para>
388
389 <para>
390 If the fileserver is not running a recent version of linux, you may
391 need to specify other options.
392 </para>
393
394 <para revision="systemd">
395 You may need to enable autofs v4 in your kernel, and add the option
396 <literal>comment=systemd.automount</literal>. Some machines may need
397 this because systemd tries to mount the external filesystems before
398 the network is up. An alternative is to run <command>mount -a</command>
399 as the <systemitem class="username">root</systemitem> user after the
400 system has started.
401 </para>
402
403 <indexterm zone="nfs-utils nfs-utils-client-config">
404 <primary sortas="e-etc-fstab">/etc/fstab</primary>
405 </indexterm>
406
407 <sect4 id="nfs-utils-client-init">
408 <title><phrase revision="sysv">Boot Script</phrase>
409 <phrase revision="systemd">Systemd Units</phrase></title>
410
411 <note>
412 <para>
413 The following <phrase revision="sysv">boot script is</phrase>
414 <phrase revision="systemd">systemd units are</phrase> not required
415 if the nfs-server <phrase revision="sysv">script is</phrase>
416 <phrase revision="systemd">units are</phrase> installed.
417 </para>
418 </note>
419
420 <para>
421 Install the
422 <phrase revision="sysv">
423 <filename>/etc/rc.d/init.d/nfs-client</filename> init script
424 </phrase>
425 <phrase revision="systemd">units</phrase> included in the
426 <xref linkend="bootscripts" revision="sysv"/>
427 <xref linkend="systemd-units" revision="systemd"/> package to start
428 the client services at boot.
429 </para>
430
431<screen role="root"><userinput>make install-nfs-client</userinput></screen>
432
433 <indexterm zone="nfs-utils nfs-utils-client-config">
434 <primary sortas="f-nfs-client">nfs-client</primary>
435 </indexterm>
436
437 <para revision="sysv">
438 To automatically mount <systemitem class="filesystem">nfs
439 </systemitem> filesystems, clients will also need to install the
440 <filename>netfs</filename> bootscript as described in <xref
441 linkend="postlfs-config-netfs"/>.
442 </para>
443
444 <indexterm zone="nfs-utils nfs-utils-client-config" revision="sysv">
445 <primary sortas="f-netfs">netfs</primary>
446 </indexterm>
447
448 </sect4>
449
450 </sect3>
451
452 </sect2>
453
454 <sect2 role="content">
455 <title>Contents</title>
456 <segmentedlist>
457 <segtitle>Installed Programs</segtitle>
458 <segtitle>Installed Libraries</segtitle>
459 <segtitle>Installed Directories</segtitle>
460
461 <seglistitem>
462 <seg>exportfs, fsidd, mountstats, mount.nfs, mount.nfs4 (link to mount.nfs),
463 nfsconf, nfsdclnts, nfsiostat, nfsstat, rpc.mountd, rpc.nfsd, rpc.statd,
464 rpcdebug, showmount, sm-notify, start-statd,
465 umount.nfs (link to mount.nfs), and umount.nfs4 (link to mount.nfs)</seg>
466 <seg>None</seg>
467 <seg>/var/lib/nfs</seg>
468 </seglistitem>
469 </segmentedlist>
470
471 <variablelist>
472 <bridgehead renderas="sect3">Short Descriptions</bridgehead>
473 <?dbfo list-presentation="list"?>
474 <?dbhtml list-presentation="table"?>
475
476 <varlistentry id="exportfs">
477 <term><command>exportfs</command></term>
478 <listitem>
479 <para>
480 maintains a list of NFS exported file systems
481 </para>
482 <indexterm zone="nfs-utils exportfs">
483 <primary sortas="b-exportfs">exportfs</primary>
484 </indexterm>
485 </listitem>
486 </varlistentry>
487
488 <varlistentry id="fsidd">
489 <term><command>fsidd</command></term>
490 <listitem>
491 <para>
492 offers a local UNIX domain socket interface
493 for all NFS userspace to query the reexport database
494 </para>
495 <indexterm zone="nfs-utils fsidd">
496 <primary sortas="b-fsidd">fsidd</primary>
497 </indexterm>
498 </listitem>
499 </varlistentry>
500
501 <varlistentry id="mountstats">
502 <term><command>mountstats</command></term>
503 <listitem>
504 <para>
505 displays NFS client per-mount statistics
506 </para>
507 <indexterm zone="nfs-utils mountstats">
508 <primary sortas="b-mountstats">mountstats</primary>
509 </indexterm>
510 </listitem>
511 </varlistentry>
512
513 <varlistentry id="mount.nfs">
514 <term><command>mount.nfs</command></term>
515 <listitem>
516 <para>
517 is used to mount a network share using NFS
518 </para>
519 <indexterm zone="nfs-utils mount.nfs">
520 <primary sortas="b-mount.nfs">mount.nfs</primary>
521 </indexterm>
522 </listitem>
523 </varlistentry>
524
525 <varlistentry id="mount.nfs4">
526 <term><command>mount.nfs4</command></term>
527 <listitem>
528 <para>
529 is used to mount a network share using NFSv4
530 </para>
531 <indexterm zone="nfs-utils mount.nfs4">
532 <primary sortas="b-mount.nfs4">mount.nfs4</primary>
533 </indexterm>
534 </listitem>
535 </varlistentry>
536
537 <varlistentry id="nfsconf">
538 <term><command>nfsconf</command></term>
539 <listitem>
540 <para>
541 can be used to test for and retrieve configuration settings from
542 a range of nfs-utils configuration files
543 </para>
544 <indexterm zone="nfs-utils nfsconf">
545 <primary sortas="b-nfsconf">nfsconf</primary>
546 </indexterm>
547 </listitem>
548 </varlistentry>
549
550 <varlistentry id="nfsdclnts">
551 <term><command>nfsdclnts</command></term>
552 <listitem>
553 <para>
554 prints information about NFS clients
555 </para>
556 <indexterm zone="nfs-utils nfsdclnts">
557 <primary sortas="b-nfsdclnts">nfsdclnts</primary>
558 </indexterm>
559 </listitem>
560 </varlistentry>
561
562 <varlistentry id="nfsiostat-nfs-utils">
563 <term><command>nfsiostat</command></term>
564 <listitem>
565 <para>
566 reports input/output statistics for network filesystems
567 </para>
568 <indexterm zone="nfs-utils nfsiostat-nfs-utils">
569 <primary sortas="b-nfsiostat-nfs-utils">nfsiostat</primary>
570 </indexterm>
571 </listitem>
572 </varlistentry>
573
574 <varlistentry id="nfsstat">
575 <term><command>nfsstat</command></term>
576 <listitem>
577 <para>
578 displays statistics kept about NFS client and server activity
579 </para>
580 <indexterm zone="nfs-utils nfsstat">
581 <primary sortas="b-nfsstat">nfsstat</primary>
582 </indexterm>
583 </listitem>
584 </varlistentry>
585
586<!-- osd_login seems to no longer exist.
587 <varlistentry id="osd_login">
588 <term><command>osd_login</command></term>
589 <listitem>
590 <para>
591 is a script that is a part of the autologin feature
592 mandated by the pnfs-objects standard.
593 </para>
594 <indexterm zone="nfs-utils osd_login">
595 <primary sortas="b-osd_login">osd_login</primary>
596 </indexterm>
597 </listitem>
598 </varlistentry> -->
599
600
601 <varlistentry id="rpc.mountd">
602 <term><command>rpc.mountd</command></term>
603 <listitem>
604 <para>
605 implements the NFS mount protocol on an NFS server
606 </para>
607 <indexterm zone="nfs-utils rpc.mountd">
608 <primary sortas="b-rpc.mountd">rpc.mountd</primary>
609 </indexterm>
610 </listitem>
611 </varlistentry>
612
613 <varlistentry id="rpc.nfsd">
614 <term><command>rpc.nfsd</command></term>
615 <listitem>
616 <para>
617 implements the user level part of the NFS
618 service on the server
619 </para>
620 <indexterm zone="nfs-utils rpc.nfsd">
621 <primary sortas="b-rpc.nfsd">rpc.nfsd</primary>
622 </indexterm>
623 </listitem>
624 </varlistentry>
625
626 <varlistentry id="rpc.statd">
627 <term><command>rpc.statd</command></term>
628 <listitem>
629 <para>
630 is used by the NFS file locking service. Run on both sides,
631 client as well as server, when you want file locking enabled
632 </para>
633 <indexterm zone="nfs-utils rpc.statd">
634 <primary sortas="b-rpc.statd">rpc.statd</primary>
635 </indexterm>
636 </listitem>
637 </varlistentry>
638
639 <varlistentry id="rpcdebug">
640 <term><command>rpcdebug</command></term>
641 <listitem>
642 <para>
643 sets or clears the kernel's NFS client and server debug flags
644 </para>
645 <indexterm zone="nfs-utils rpcdebug">
646 <primary sortas="b-rpcdebug">rpcdebug</primary>
647 </indexterm>
648 </listitem>
649 </varlistentry>
650
651 <varlistentry id="showmount">
652 <term><command>showmount</command></term>
653 <listitem>
654 <para>
655 displays mount information for an NFS server
656 </para>
657 <indexterm zone="nfs-utils showmount">
658 <primary sortas="b-showmount">showmount</primary>
659 </indexterm>
660 </listitem>
661 </varlistentry>
662
663 <varlistentry id="sm-notify">
664 <term><command>sm-notify</command></term>
665 <listitem>
666 <para>
667 is used to send Network Status Monitor reboot messages
668 </para>
669 <indexterm zone="nfs-utils sm-notify">
670 <primary sortas="b-sm-notify">sm-notify</primary>
671 </indexterm>
672 </listitem>
673 </varlistentry>
674
675 <varlistentry id="start-statd">
676 <term><command>start-statd</command></term>
677 <listitem>
678 <para>
679 is a script called by nfsmount when mounting a filesystem with
680 locking enabled, if statd does not appear to be running. It can be
681 customised with whatever flags are appropriate for the site
682 </para>
683 <indexterm zone="nfs-utils start-statd">
684 <primary sortas="b-start-statd">start-statd</primary>
685 </indexterm>
686 </listitem>
687 </varlistentry>
688
689 <varlistentry id="umount.nfs">
690 <term><command>umount.nfs</command></term>
691 <listitem>
692 <para>
693 is used to unmount a network share using NFS
694 </para>
695 <indexterm zone="nfs-utils umount.nfs">
696 <primary sortas="b-umount.nfs">umount.nfs</primary>
697 </indexterm>
698 </listitem>
699 </varlistentry>
700
701 <varlistentry id="umount.nfs4">
702 <term><command>umount.nfs4</command></term>
703 <listitem>
704 <para>
705 is used to unmount a network share using NFSv4
706 </para>
707 <indexterm zone="nfs-utils umount.nfs4">
708 <primary sortas="b-umount.nfs4">umount.nfs4</primary>
709 </indexterm>
710 </listitem>
711 </varlistentry>
712
713 </variablelist>
714
715 </sect2>
716
717</sect1>
Note: See TracBrowser for help on using the repository browser.