source: networking/netprogs/nfs-utils.xml@ 6ca13da3

12.0 12.1 kea ken/TL2024 ken/tuningfonts lazarus lxqt plabs/newcss python3.11 rahul/power-profiles-daemon renodr/vulkan-addition trunk xry111/llvm18 xry111/xf86-video-removal
Last change on this file since 6ca13da3 was bc7af21, checked in by Pierre Labastie <pierre.labastie@…>, 13 months ago

Fix test instructions in nfs-utils

When test instructions need to be run as root, it is not enough to
use a <command> tag. It needs a <screen> tag with role="root" and
remap="test" attributes.

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