source: networking/netprogs/nfs-utils.xml@ 6df48a7

10.0 10.1 11.0 ken/refactor-virt lazarus qt5new trunk xry111/git-date xry111/git-date-for-trunk xry111/git-date-test
Last change on this file since 6df48a7 was 6df48a7, checked in by Bruce Dubbs <bdubbs@…>, 16 months ago

Update to nfs-utils-2.5.1.

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@23318 af4574ff-66df-0310-9fd7-8a98e5e911e0

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