source: networking/netprogs/nfs-utils.xml@ c5d6597

12.0 12.1 ken/TL2024 ken/tuningfonts lazarus plabs/newcss python3.11 rahul/power-profiles-daemon renodr/vulkan-addition trunk xry111/llvm18
Last change on this file since c5d6597 was ddf1885b, checked in by Bruce Dubbs <bdubbs@…>, 10 months ago

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