source: networking/netprogs/nfs-utils.xml@ 758f3f6

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 758f3f6 was 758f3f6, checked in by Douglas R. Reno <renodr@…>, 4 years ago

Update to xfsprogs-5.9.0
Update to alsa-lib, alsa-utils, and alsa-firmware-1.2.4
Update to faad2-2_10_0
Update to poppler-data-0.4.10
Update to List-MoreUtils-XS-0.430 (Perl Module)
Update to List-MoreUtils-0.430 (Perl Module)
Update to URI-5.05 (Perl Module)
Update to bind9 and bind-utils 9.16.8
Update to nfs-utils-2.5.2

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@23834 af4574ff-66df-0310-9fd7-8a98e5e911e0
  • 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 "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 &lfs10_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 <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 /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
250 <para>
251 <parameter>--disable-gss</parameter>: Disables support for
252 RPCSEC GSS (RPC Security).
253 </para>
254
255 <para>
256 <command>chown nobody.nogroup /var/lib/nfs</command>: The
257 rpc.statd program uses the ownership of this directory to set
258 it's UID and GID. This command sets those to unprivileged entries.
259 </para>
260
261 </sect2>
262
263 <sect2 role="configuration">
264 <title>Configuring NFS Utilities</title>
265
266 <sect3 id='nfs-utils-server-config'>
267 <title>Server Configuration</title>
268
269 <para>
270 <filename>/etc/exports</filename> contains the exported directories
271 on NFS servers. Refer to the <filename>exports.5</filename> manual page
272 for the syntax of this file. Also refer to the "NFS HowTo" available at
273 <ulink url="http://nfs.sourceforge.net/nfs-howto/"/> for information on
274 how to configure the servers and clients in a secure manner. For
275 example, for sharing the <filename class="directory">/home</filename>
276 directory over the local network, the following line may be added:
277 </para>
278
279<screen role="nodump"><userinput>cat &gt;&gt; /etc/exports &lt;&lt; EOF
280<replaceable>/home 192.168.0.0/24</replaceable>(rw,subtree_check,anonuid=99,anongid=99)
281EOF</userinput></screen>
282
283 <note>
284 <para>
285 Be sure to replace the directory, network address. and prefix above
286 to match your network. The only space in the line above should be
287 between the directory and the network address.
288 </para>
289 </note>
290
291 <indexterm zone="nfs-utils nfs-utils-server-config">
292 <primary sortas="e-etc-exportfs">/etc/exportfs</primary>
293 </indexterm>
294
295 <sect4 id="nfs-utils-server-init">
296 <title><phrase revision="sysv">Boot Script</phrase>
297 <phrase revision="systemd">Systemd Units</phrase></title>
298
299 <para>
300 Install the
301 <phrase revision="sysv">
302 <filename>/etc/rc.d/init.d/nfs-server</filename>
303 init script
304 </phrase>
305 <phrase revision="systemd">NFSv4 server units</phrase>
306 included in the <xref linkend="bootscripts" revision="sysv"/>
307 <xref linkend="systemd-units" revision="systemd"/> package
308 to start the server at boot.
309 </para>
310
311<screen role="root" revision="systemd"><userinput>make install-nfsv4-server</userinput></screen>
312
313 <para revision="systemd">
314 If you have disabled NFSv4 support, run the following command as the
315 <systemitem class="username">root</systemitem> user to omit the NFSv4
316 specific systemd units:
317 </para>
318
319<!-- both -->
320<screen role="root"><userinput>make install-nfs-server</userinput></screen>
321
322 <indexterm zone="nfs-utils nfs-utils-server-init" revision="sysv">
323 <primary sortas="f-nfs-server">nfs-server</primary>
324 </indexterm>
325
326 <para revision="sysv">
327 Now create the
328 <filename>/etc/sysconfig/nfs-server</filename> configuration file:
329 </para>
330
331<screen role="root" revision="sysv"><userinput>cat &gt; /etc/sysconfig/nfs-server &lt;&lt; "EOF"
332<literal>PORT="2049"
333PROCESSES="8"
334KILLDELAY="10"</literal>
335EOF</userinput></screen>
336
337 <note revision="sysv">
338 <para>
339 The above parameters may be optionally placed in
340 <filename>/etc/sysconfig/rc.site</filename>.
341 </para>
342 </note>
343
344 <indexterm zone="nfs-utils nfs-utils-server-init" revision="sysv">
345 <primary
346 sortas="e-etc-sysconfig-nfs-server">/etc/sysconfig/nfs-server</primary>
347 </indexterm>
348
349 <para revision="systemd">
350 You can edit the <filename>/etc/default/nfs-utils</filename>
351 file to change the startup options for NFS daemons. Defaults
352 should be fine for most use cases.
353 </para>
354
355 <indexterm zone="nfs-utils nfs-utils-server-init" revision="systemd">
356 <primary sortas="e-etc-default-nfs-utils">/etc/default/nfs-utils</primary>
357 </indexterm>
358
359 </sect4>
360
361 </sect3>
362
363 <sect3 id='nfs-utils-client-config'>
364 <title>Client Configuration</title>
365
366 <para>
367 <filename>/etc/fstab</filename> contains the directories that
368 are to be mounted on the client. Alternately the partitions can be
369 mounted by using the <command>mount</command> command with the proper
370 options. To mount the <filename class="directory">/home</filename>
371 and <filename class="directory">/usr</filename> partitions, add the
372 following to the <filename>/etc/fstab</filename>:
373 </para>
374
375<screen role="nodump"><userinput><replaceable>&lt;server-name&gt;</replaceable>:/home /home nfs rw,_netdev 0 0
376<replaceable>&lt;server-name&gt;</replaceable>:/usr /usr nfs ro,_netdev 0 0</userinput></screen>
377
378 <para>
379 The options which can be used are specified in <command>man 5 nfs
380 </command>. If both the client and server are running recent versions
381 of linux, most of the options will be negotiated (but see the Note
382 above on nfsver=3). You can specify either <literal>rw</literal> or
383 <literal>ro</literal>, <literal>_netdev</literal> if the filesystem is
384 to be automatically mounted at boot, or <literal>noauto</literal> (and
385 perhaps <literal>user</literal>) for other filesystems.
386 </para>
387
388 <para>
389 If the fileserver is not running a recent version of linux, you may
390 need to specifiy other options.
391 </para>
392
393 <para revision="systemd">
394 You may need to enable autofs v4 in your kernel, and add the option
395 <literal>comment=systemd.automount</literal>. Some machines may need
396 this because systemd tries to mount the external filesystems before
397 the network is up. An alternative is to run <command>mount -a</command>
398 as the <systemitem class="username">root</systemitem> user after the
399 system has started.
400 </para>
401
402 <indexterm zone="nfs-utils nfs-utils-client-config">
403 <primary sortas="e-etc-fstab">/etc/fstab</primary>
404 </indexterm>
405
406 <sect4 id="nfs-utils-client-init">
407 <title><phrase revision="sysv">Boot Script</phrase>
408 <phrase revision="systemd">Systemd Units</phrase></title>
409
410 <note>
411 <para>
412 The following <phrase revision="sysv">boot script is</phrase>
413 <phrase revision="systemd">systemd units are</phrase> not required
414 if the nfs-server <phrase revision="sysv">script is</phrase>
415 <phrase revision="systemd">units are</phrase> installed.
416 </para>
417 </note>
418
419 <para>
420 Install the
421 <phrase revision="sysv">
422 <filename>/etc/rc.d/init.d/nfs-client</filename> init script
423 </phrase>
424 <phrase revision="systemd">units</phrase> included in the
425 <xref linkend="bootscripts" revision="sysv"/>
426 <xref linkend="systemd-units" revision="systemd"/> package to start
427 the client services at boot.
428 </para>
429
430<screen role="root"><userinput>make install-nfs-client</userinput></screen>
431
432 <indexterm zone="nfs-utils nfs-utils-client-config">
433 <primary sortas="f-nfs-client">nfs-client</primary>
434 </indexterm>
435
436 <para revision="sysv">
437 To automatically mount <systemitem class="filesystem">nfs
438 </systemitem> filesystems, clients will also need to install the
439 <filename>netfs</filename> bootscript as described in <xref
440 linkend="postlfs-config-netfs"/>.
441 </para>
442
443 <indexterm zone="nfs-utils nfs-utils-client-config" revision="sysv">
444 <primary sortas="f-netfs">netfs</primary>
445 </indexterm>
446
447 </sect4>
448
449 </sect3>
450
451 </sect2>
452
453 <sect2 role="content">
454 <title>Contents</title>
455 <segmentedlist>
456 <segtitle>Installed Programs</segtitle>
457 <segtitle>Installed Libraries</segtitle>
458 <segtitle>Installed Directories</segtitle>
459
460 <seglistitem>
461 <seg>exportfs, mountstats, mount.nfs, mount.nfs4 (link to mount.nfs),
462 nfsconf, nfsdclnts, nfsiostat, nfsstat, rpc.mountd, rpc.nfsd, rpc.statd,
463 rpcdebug, showmount, sm-notify, start-statd,
464 umount.nfs (link to mount.nfs), and umount.nfs4 (link to mount.nfs)</seg>
465 <seg>None</seg>
466 <seg>/var/lib/nfs</seg>
467 </seglistitem>
468 </segmentedlist>
469
470 <variablelist>
471 <bridgehead renderas="sect3">Short Descriptions</bridgehead>
472 <?dbfo list-presentation="list"?>
473 <?dbhtml list-presentation="table"?>
474
475 <varlistentry id="exportfs">
476 <term><command>exportfs</command></term>
477 <listitem>
478 <para>
479 maintains a list of NFS exported file systems.
480 </para>
481 <indexterm zone="nfs-utils exportfs">
482 <primary sortas="b-exportfs">exportfs</primary>
483 </indexterm>
484 </listitem>
485 </varlistentry>
486
487 <varlistentry id="mountstats">
488 <term><command>mountstats</command></term>
489 <listitem>
490 <para>
491 displays NFS client per-mount statistics.
492 </para>
493 <indexterm zone="nfs-utils mountstats">
494 <primary sortas="b-mountstats">mountstats</primary>
495 </indexterm>
496 </listitem>
497 </varlistentry>
498
499 <varlistentry id="mount.nfs">
500 <term><command>mount.nfs</command></term>
501 <listitem>
502 <para>
503 is used to mount a network share using NFS.
504 </para>
505 <indexterm zone="nfs-utils mount.nfs">
506 <primary sortas="b-mount.nfs">mount.nfs</primary>
507 </indexterm>
508 </listitem>
509 </varlistentry>
510
511 <varlistentry id="mount.nfs4">
512 <term><command>mount.nfs4</command></term>
513 <listitem>
514 <para>
515 is used to mount a network share using NFSv4.
516 </para>
517 <indexterm zone="nfs-utils mount.nfs4">
518 <primary sortas="b-mount.nfs4">mount.nfs4</primary>
519 </indexterm>
520 </listitem>
521 </varlistentry>
522
523 <varlistentry id="nfsconf">
524 <term><command>nfsconf</command></term>
525 <listitem>
526 <para>
527 can be used to test for and retrieve configuration settings from
528 a range of nfs-utils configuration files.
529 </para>
530 <indexterm zone="nfs-utils nfsconf">
531 <primary sortas="b-nfsconf">nfsconf</primary>
532 </indexterm>
533 </listitem>
534 </varlistentry>
535
536 <varlistentry id="nfsdclnts">
537 <term><command>nfsdclnts</command></term>
538 <listitem>
539 <para>
540 prints information about NFS clients.
541 </para>
542 <indexterm zone="nfs-utils nfsdclnts">
543 <primary sortas="b-nfsdclnts">nfsdclnts</primary>
544 </indexterm>
545 </listitem>
546 </varlistentry>
547
548 <varlistentry id="nfsiostat-nfs-utils">
549 <term><command>nfsiostat</command></term>
550 <listitem>
551 <para>
552 reports input/output statistics for network filesystems.
553 </para>
554 <indexterm zone="nfs-utils nfsiostat-nfs-utils">
555 <primary sortas="b-nfsiostat-nfs-utils">nfsiostat</primary>
556 </indexterm>
557 </listitem>
558 </varlistentry>
559
560 <varlistentry id="nfsstat">
561 <term><command>nfsstat</command></term>
562 <listitem>
563 <para>
564 displays statistics kept about NFS client and server activity.
565 </para>
566 <indexterm zone="nfs-utils nfsstat">
567 <primary sortas="b-nfsstat">nfsstat</primary>
568 </indexterm>
569 </listitem>
570 </varlistentry>
571
572<!-- osd_login seems to no longer exist.
573 <varlistentry id="osd_login">
574 <term><command>osd_login</command></term>
575 <listitem>
576 <para>
577 is a script that is a part of the autologin feature
578 mandated by the pnfs-objects standard.
579 </para>
580 <indexterm zone="nfs-utils osd_login">
581 <primary sortas="b-osd_login">osd_login</primary>
582 </indexterm>
583 </listitem>
584 </varlistentry> -->
585
586
587 <varlistentry id="rpc.mountd">
588 <term><command>rpc.mountd</command></term>
589 <listitem>
590 <para>
591 implements the NFS mount protocol on an NFS server.
592 </para>
593 <indexterm zone="nfs-utils rpc.mountd">
594 <primary sortas="b-rpc.mountd">rpc.mountd</primary>
595 </indexterm>
596 </listitem>
597 </varlistentry>
598
599 <varlistentry id="rpc.nfsd">
600 <term><command>rpc.nfsd</command></term>
601 <listitem>
602 <para>
603 implements the user level part of the NFS
604 service on the server.
605 </para>
606 <indexterm zone="nfs-utils rpc.nfsd">
607 <primary sortas="b-rpc.nfsd">rpc.nfsd</primary>
608 </indexterm>
609 </listitem>
610 </varlistentry>
611
612 <varlistentry id="rpc.statd">
613 <term><command>rpc.statd</command></term>
614 <listitem>
615 <para>
616 is used by the NFS file locking service. Run on both sides,
617 client as well as server, when you want file locking enabled.
618 </para>
619 <indexterm zone="nfs-utils rpc.statd">
620 <primary sortas="b-rpc.statd">rpc.statd</primary>
621 </indexterm>
622 </listitem>
623 </varlistentry>
624
625 <varlistentry id="rpcdebug">
626 <term><command>rpcdebug</command></term>
627 <listitem>
628 <para>
629 sets or clears the kernel's NFS client and server debug flags.
630 </para>
631 <indexterm zone="nfs-utils rpcdebug">
632 <primary sortas="b-rpcdebug">rpcdebug</primary>
633 </indexterm>
634 </listitem>
635 </varlistentry>
636
637 <varlistentry id="showmount">
638 <term><command>showmount</command></term>
639 <listitem>
640 <para>
641 displays mount information for an NFS server.
642 </para>
643 <indexterm zone="nfs-utils showmount">
644 <primary sortas="b-showmount">showmount</primary>
645 </indexterm>
646 </listitem>
647 </varlistentry>
648
649 <varlistentry id="sm-notify">
650 <term><command>sm-notify</command></term>
651 <listitem>
652 <para>
653 is used to send Network Status Monitor reboot messages.
654 </para>
655 <indexterm zone="nfs-utils sm-notify">
656 <primary sortas="b-sm-notify">sm-notify</primary>
657 </indexterm>
658 </listitem>
659 </varlistentry>
660
661 <varlistentry id="start-statd">
662 <term><command>start-statd</command></term>
663 <listitem>
664 <para>
665 is a script called by nfsmount when mounting a filesystem with
666 locking enabled, if statd does not appear to be running. It can be
667 customised with whatever flags are appropriate for the site.
668 </para>
669 <indexterm zone="nfs-utils start-statd">
670 <primary sortas="b-start-statd">start-statd</primary>
671 </indexterm>
672 </listitem>
673 </varlistentry>
674
675 <varlistentry id="umount.nfs">
676 <term><command>umount.nfs</command></term>
677 <listitem>
678 <para>
679 is used to unmount a network share using NFS.
680 </para>
681 <indexterm zone="nfs-utils umount.nfs">
682 <primary sortas="b-umount.nfs">umount.nfs</primary>
683 </indexterm>
684 </listitem>
685 </varlistentry>
686
687 <varlistentry id="umount.nfs4">
688 <term><command>umount.nfs4</command></term>
689 <listitem>
690 <para>
691 is used to unmount a network share using NFSv4.
692 </para>
693 <indexterm zone="nfs-utils umount.nfs4">
694 <primary sortas="b-umount.nfs4">umount.nfs4</primary>
695 </indexterm>
696 </listitem>
697 </varlistentry>
698
699 </variablelist>
700
701 </sect2>
702
703</sect1>
Note: See TracBrowser for help on using the repository browser.