source: networking/netprogs/nfs-utils.xml@ 57cc7a3

trunk
Last change on this file since 57cc7a3 was 57cc7a3, checked in by Bruce Dubbs <bdubbs@…>, 8 weeks ago

Package updates.
Update to gnome-terminal-3.40.2.
Update to vte-0.64.2.
Update to libogg-1.3.5.
Update to nfs-utils-2.5.3.
Update to librsvg-2.50.7.
Update to libqmi-1.28.6.
Update to dash-0.5.11.4.

  • Property mode set to 100644
File size: 24.2 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 "24353242a96549fc697d25dc29a961db">
11 <!ENTITY nfs-utils-size "684 KB">
12 <!ENTITY nfs-utils-buildsize "16 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 <date>$Date$</date>
21 </sect1info>
22
23 <title>NFS-Utils-&nfs-utils-version;</title>
24
25 <indexterm zone="nfs-utils">
26 <primary sortas="a-Nfs-utils">NFS Utilities</primary>
27 </indexterm>
28
29 <sect2 role="package">
30 <title>Introduction to NFS Utilities</title>
31
32 <para>
33 The <application>NFS Utilities</application> package contains the
34 userspace server and client tools necessary to use the kernel's NFS
35 abilities. NFS is a protocol that allows sharing file systems over the
36 network.
37 </para>
38
39 &lfs101_checked;
40
41 <bridgehead renderas="sect3">Package Information</bridgehead>
42 <itemizedlist spacing='compact'>
43 <listitem>
44 <para>
45 Download (HTTP): <ulink url="&nfs-utils-download-http;"/>
46 </para>
47 </listitem>
48 <listitem>
49 <para>
50 Download (FTP): <ulink url="&nfs-utils-download-ftp;"/>
51 </para>
52 </listitem>
53 <listitem>
54 <para>
55 Download MD5 sum: &nfs-utils-md5sum;
56 </para>
57 </listitem>
58 <listitem>
59 <para>
60 Download size: &nfs-utils-size;
61 </para>
62 </listitem>
63 <listitem>
64 <para>
65 Estimated disk space required: &nfs-utils-buildsize;
66 </para>
67 </listitem>
68 <listitem>
69 <para>
70 Estimated build time: &nfs-utils-time;
71 </para>
72 </listitem>
73 </itemizedlist>
74
75 <bridgehead renderas="sect3">NFS Utilities Dependencies</bridgehead>
76
77 <bridgehead renderas="sect4">Required</bridgehead>
78 <para role="required">
79 <xref linkend="libtirpc"/> and
80 <xref linkend="rpcsvc-proto"/>
81 </para>
82
83 <bridgehead renderas="sect4">Optional</bridgehead>
84 <para role="optional">
85 <xref linkend="cyrus-sasl"/> (for SASL authentication),
86 <xref linkend="lvm2"/> (libdevmapper for NFSv4 support),
87 <!--<xref linkend="libnfsidmap"/> (for NFSv4 support),
88 This is now built in, as of 2.2.1-->
89 <xref linkend="libnsl"/> (for NIS client support),
90 <xref linkend="openldap"/> (for LDAP authentication),
91 <xref linkend="sqlite"/>,
92 <xref linkend="mitkrb"/> or
93 <ulink url="http://www.citi.umich.edu/projects/nfsv4/linux/">
94 libgssapi
95 </ulink>, and
96 <ulink url="http://www.citi.umich.edu/projects/nfsv4/linux/">
97 librpcsecgss
98 </ulink> (for GSS and RPC security support), and
99 <xref linkend="libcap-pam"/>
100 </para>
101
102 <bridgehead renderas="sect4">Required (runtime)</bridgehead>
103 <para role="required">
104 <xref role="runtime" linkend="rpcbind"/>
105 </para>
106
107<!-- NSS configuration isn't directly related to NFS, but left here in case
108 <bridgehead renderas="sect4">Optional (runtime for NIS clients)</bridgehead>
109 <para role="optional">
110 <ulink url="https://github.com/thkukuk/libnss_compat">libnss_compat</ulink>,
111 <ulink url="https://github.com/thkukuk/libnss_nis">libnss_nis</ulink>, and
112 <ulink url="https://github.com/thkukuk/libnss_nisplus">libnss_nisplus</ulink>
113 </para>
114-->
115
116 <para condition="html" role="usernotes">User Notes:
117 <ulink url="&blfs-wiki;/nfs-utils"/></para>
118
119 </sect2>
120
121 <sect2 role="kernel" id='nfs-utils-kernel'>
122 <title>Kernel Configuration</title>
123
124 <para>
125 Enable the following options in the kernel configuration
126 (choose client and/or server support as appropriate) and recompile the
127 kernel if necessary:
128 </para>
129
130<screen><literal>File systems ---&gt;
131 [*] Network File Systems ---&gt; [CONFIG_NETWORK_FILESYSTEMS]
132 &lt;*/M&gt; NFS client support [CONFIG_NFS_FS]
133 &lt;*/M&gt; NFS server support [CONFIG_NFSD]</literal></screen>
134
135 <para>
136 Select the appropriate sub-options that appear when the above options
137 are selected.
138 </para>
139
140 <note>
141 <para>
142 In BLFS we assume that nfs v3 will be used. If the
143 <emphasis>server</emphasis> offers nfs v4 (for linux, CONFIG_NFSD_V4)
144 then auto-negotiation for v3 will fail and you will need to add
145 <literal>nfsver=3</literal> to the mount options. This also applies
146 if that option is enabled in the <emphasis>client's</emphasis> kernel,
147 for example in a distro trying to mount from a BLFS v3 server.
148 </para>
149 <para>
150 Even if neither end of the connection supports nfs v4, adding
151 <literal>nfsver=3</literal> is still beneficial because it prevents an
152 error message "NFS: bad mount option value specified: minorversion=1"
153 being logged on every mount.
154 </para>
155 </note>
156
157 <indexterm zone="nfs-utils nfs-utils-kernel">
158 <primary sortas="d-nfs-utils">NFS Utilities</primary>
159 </indexterm>
160
161 </sect2>
162
163 <sect2 role="installation" id='nfs-utils-install'
164 xreflabel='NFS Utilities Installation'>
165 <title>Installation of NFS Utilities</title>
166
167 <para>
168 Before you compile the program, ensure that the <systemitem
169 class="username">nobody</systemitem> user and <systemitem
170 class="groupname">nogroup</systemitem> group have been created as done in
171 the current LFS book. You can add them by running the following commands
172 as the <systemitem class="username">root</systemitem> user:
173 </para>
174
175<screen role="nodump"><userinput>groupadd -g 99 nogroup &amp;&amp;
176useradd -c "Unprivileged Nobody" -d /dev/null -g nogroup \
177 -s /bin/false -u 99 nobody</userinput></screen>
178
179 <note>
180 <para>
181 The classic uid and gid values are 65534 which is also -2 when
182 interpreted as a signed 16-bit number. These values impact other files
183 on some filesystems that do not have support for sparse files. The
184 <systemitem class="username">nobody</systemitem> and <systemitem
185 class="groupname">nogroup</systemitem> values are relatively arbitrary.
186 The impact on a server is nil if the <filename>exports</filename> file
187 is configured correctly. If it is misconfigured, an
188 <command>ls -l</command> or <command>ps</command> listing will show a
189 uid or gid number of 65534 instead of a name. The client uses
190 <systemitem class="username">nobody</systemitem> only as the user
191 running <command>rpc.statd</command>.
192 </para>
193 </note>
194
195 <para>
196 Install <application>NFS Utilities</application> by running
197 the following commands:
198 </para>
199
200<screen><userinput>./configure --prefix=/usr \
201 --sysconfdir=/etc \
202 --sbindir=/sbin \
203 --disable-nfsv4 \
204 --disable-gss &amp;&amp;
205make</userinput></screen>
206
207 <!-- Test breakage: see
208 http://lists.linuxfromscratch.org/pipermail/blfs-book/2017-December/071861.html -->
209 <para>
210 This package does not come with a working test suite.
211 </para>
212
213 <para>
214 Now, as the <systemitem class="username">root</systemitem> user:
215 </para>
216
217<!-- dev note: make statduser=$(whoami) DESTDIR=<DESTDIR> install -->
218
219<screen role='root'><userinput>make install &amp;&amp;
220chmod u+w,go+r /usr/sbin/mount.nfs &amp;&amp;
221chown nobody.nogroup /var/lib/nfs</userinput></screen>
222
223 <!-- commented, in case the tests get fixed
224 <para>
225 The tests for this package require that the package be installed and
226 configured as specified below. In addition, the daemon from <xref
227 linkend="rpcbind"/> needs to be running and the tests need to be run as
228 the <systemitem class="username">root</systemitem> user.
229 </para>
230
231 <para>
232 To test the results, issue, as root: <command>make check</command>.
233 </para>-->
234
235 </sect2>
236
237 <sect2 role="commands">
238 <title>Command Explanations</title>
239<!--
240 <para>
241 <command>sed ... support/nsm/rpc.c</command>: This sed it required
242 to fix a build issue with glibc-2.26 and later.
243 </para>
244
245 <para>
246 <parameter>- -disable-nfsv4</parameter>: This allows the package to be
247 built when libnfsidmap has not been installed.
248 </para>
249 nfs-utils now carries libnfsidmap
250-->
251 <para>
252 <parameter>--disable-gss</parameter>: Disables support for
253 RPCSEC GSS (RPC Security).
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="http://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 specifiy 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, 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="mountstats">
489 <term><command>mountstats</command></term>
490 <listitem>
491 <para>
492 displays NFS client per-mount statistics
493 </para>
494 <indexterm zone="nfs-utils mountstats">
495 <primary sortas="b-mountstats">mountstats</primary>
496 </indexterm>
497 </listitem>
498 </varlistentry>
499
500 <varlistentry id="mount.nfs">
501 <term><command>mount.nfs</command></term>
502 <listitem>
503 <para>
504 is used to mount a network share using NFS
505 </para>
506 <indexterm zone="nfs-utils mount.nfs">
507 <primary sortas="b-mount.nfs">mount.nfs</primary>
508 </indexterm>
509 </listitem>
510 </varlistentry>
511
512 <varlistentry id="mount.nfs4">
513 <term><command>mount.nfs4</command></term>
514 <listitem>
515 <para>
516 is used to mount a network share using NFSv4
517 </para>
518 <indexterm zone="nfs-utils mount.nfs4">
519 <primary sortas="b-mount.nfs4">mount.nfs4</primary>
520 </indexterm>
521 </listitem>
522 </varlistentry>
523
524 <varlistentry id="nfsconf">
525 <term><command>nfsconf</command></term>
526 <listitem>
527 <para>
528 can be used to test for and retrieve configuration settings from
529 a range of nfs-utils configuration files
530 </para>
531 <indexterm zone="nfs-utils nfsconf">
532 <primary sortas="b-nfsconf">nfsconf</primary>
533 </indexterm>
534 </listitem>
535 </varlistentry>
536
537 <varlistentry id="nfsdclnts">
538 <term><command>nfsdclnts</command></term>
539 <listitem>
540 <para>
541 prints information about NFS clients
542 </para>
543 <indexterm zone="nfs-utils nfsdclnts">
544 <primary sortas="b-nfsdclnts">nfsdclnts</primary>
545 </indexterm>
546 </listitem>
547 </varlistentry>
548
549 <varlistentry id="nfsiostat-nfs-utils">
550 <term><command>nfsiostat</command></term>
551 <listitem>
552 <para>
553 reports input/output statistics for network filesystems
554 </para>
555 <indexterm zone="nfs-utils nfsiostat-nfs-utils">
556 <primary sortas="b-nfsiostat-nfs-utils">nfsiostat</primary>
557 </indexterm>
558 </listitem>
559 </varlistentry>
560
561 <varlistentry id="nfsstat">
562 <term><command>nfsstat</command></term>
563 <listitem>
564 <para>
565 displays statistics kept about NFS client and server activity
566 </para>
567 <indexterm zone="nfs-utils nfsstat">
568 <primary sortas="b-nfsstat">nfsstat</primary>
569 </indexterm>
570 </listitem>
571 </varlistentry>
572
573<!-- osd_login seems to no longer exist.
574 <varlistentry id="osd_login">
575 <term><command>osd_login</command></term>
576 <listitem>
577 <para>
578 is a script that is a part of the autologin feature
579 mandated by the pnfs-objects standard.
580 </para>
581 <indexterm zone="nfs-utils osd_login">
582 <primary sortas="b-osd_login">osd_login</primary>
583 </indexterm>
584 </listitem>
585 </varlistentry> -->
586
587
588 <varlistentry id="rpc.mountd">
589 <term><command>rpc.mountd</command></term>
590 <listitem>
591 <para>
592 implements the NFS mount protocol on an NFS server
593 </para>
594 <indexterm zone="nfs-utils rpc.mountd">
595 <primary sortas="b-rpc.mountd">rpc.mountd</primary>
596 </indexterm>
597 </listitem>
598 </varlistentry>
599
600 <varlistentry id="rpc.nfsd">
601 <term><command>rpc.nfsd</command></term>
602 <listitem>
603 <para>
604 implements the user level part of the NFS
605 service on the server
606 </para>
607 <indexterm zone="nfs-utils rpc.nfsd">
608 <primary sortas="b-rpc.nfsd">rpc.nfsd</primary>
609 </indexterm>
610 </listitem>
611 </varlistentry>
612
613 <varlistentry id="rpc.statd">
614 <term><command>rpc.statd</command></term>
615 <listitem>
616 <para>
617 is used by the NFS file locking service. Run on both sides,
618 client as well as server, when you want file locking enabled
619 </para>
620 <indexterm zone="nfs-utils rpc.statd">
621 <primary sortas="b-rpc.statd">rpc.statd</primary>
622 </indexterm>
623 </listitem>
624 </varlistentry>
625
626 <varlistentry id="rpcdebug">
627 <term><command>rpcdebug</command></term>
628 <listitem>
629 <para>
630 sets or clears the kernel's NFS client and server debug flags
631 </para>
632 <indexterm zone="nfs-utils rpcdebug">
633 <primary sortas="b-rpcdebug">rpcdebug</primary>
634 </indexterm>
635 </listitem>
636 </varlistentry>
637
638 <varlistentry id="showmount">
639 <term><command>showmount</command></term>
640 <listitem>
641 <para>
642 displays mount information for an NFS server
643 </para>
644 <indexterm zone="nfs-utils showmount">
645 <primary sortas="b-showmount">showmount</primary>
646 </indexterm>
647 </listitem>
648 </varlistentry>
649
650 <varlistentry id="sm-notify">
651 <term><command>sm-notify</command></term>
652 <listitem>
653 <para>
654 is used to send Network Status Monitor reboot messages
655 </para>
656 <indexterm zone="nfs-utils sm-notify">
657 <primary sortas="b-sm-notify">sm-notify</primary>
658 </indexterm>
659 </listitem>
660 </varlistentry>
661
662 <varlistentry id="start-statd">
663 <term><command>start-statd</command></term>
664 <listitem>
665 <para>
666 is a script called by nfsmount when mounting a filesystem with
667 locking enabled, if statd does not appear to be running. It can be
668 customised with whatever flags are appropriate for the site
669 </para>
670 <indexterm zone="nfs-utils start-statd">
671 <primary sortas="b-start-statd">start-statd</primary>
672 </indexterm>
673 </listitem>
674 </varlistentry>
675
676 <varlistentry id="umount.nfs">
677 <term><command>umount.nfs</command></term>
678 <listitem>
679 <para>
680 is used to unmount a network share using NFS
681 </para>
682 <indexterm zone="nfs-utils umount.nfs">
683 <primary sortas="b-umount.nfs">umount.nfs</primary>
684 </indexterm>
685 </listitem>
686 </varlistentry>
687
688 <varlistentry id="umount.nfs4">
689 <term><command>umount.nfs4</command></term>
690 <listitem>
691 <para>
692 is used to unmount a network share using NFSv4
693 </para>
694 <indexterm zone="nfs-utils umount.nfs4">
695 <primary sortas="b-umount.nfs4">umount.nfs4</primary>
696 </indexterm>
697 </listitem>
698 </varlistentry>
699
700 </variablelist>
701
702 </sect2>
703
704</sect1>
Note: See TracBrowser for help on using the repository browser.