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

10.1 11.0 11.1 11.2 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 upgradedb xry111/intltool xry111/llvm18 xry111/soup3 xry111/test-20220226 xry111/xf86-video-removal
Last change on this file since a4ce449 was a4ce449, checked in by Thomas Trepl <thomas@…>, 3 years ago

Some more tags

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