source: networking/netprogs/nfs-utils.xml@ 6375ab4

11.3 12.0 12.1 kea ken/TL2024 ken/inkscape-core-mods ken/tuningfonts lazarus lxqt plabs/newcss plabs/python-mods python3.11 qt5new rahul/power-profiles-daemon renodr/vulkan-addition trunk xry111/llvm18 xry111/xf86-video-removal
Last change on this file since 6375ab4 was 3f2db3a6, checked in by Pierre Labastie <pierre.labastie@…>, 19 months ago

Remove sect1info tags

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