1 .\" Copyright (c) 1989, 1991, 1993
2 .\" The Regents of the University of California. All rights reserved.
4 .\" Redistribution and use in source and binary forms, with or without
5 .\" modification, are permitted provided that the following conditions
7 .\" 1. Redistributions of source code must retain the above copyright
8 .\" notice, this list of conditions and the following disclaimer.
9 .\" 2. Redistributions in binary form must reproduce the above copyright
10 .\" notice, this list of conditions and the following disclaimer in the
11 .\" documentation and/or other materials provided with the distribution.
12 .\" 3. Neither the name of the University nor the names of its contributors
13 .\" may be used to endorse or promote products derived from this software
14 .\" without specific prior written permission.
16 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
17 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
18 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
19 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
20 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
21 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
22 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
23 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
24 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
25 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
28 .\" @(#)mountd.8 8.4 (Berkeley) 4/28/95
43 .Op Ar exportsfile ...
47 utility is the server for
49 mount requests from other client machines.
50 It listens for service requests at the port indicated in the
52 server specification; see
53 .%T "Network File System Protocol Specification" ,
54 RFC1094, Appendix A and
55 .%T "NFS: Network File System Version 3 Protocol Specification" ,
58 The following options are available:
59 .Bl -tag -width indent
61 Allow the administrator to force clients to use only the
64 protocol to mount file systems from this server.
66 Output debugging information.
68 will not detach from the controlling terminal and will print
69 debugging messages to stderr.
71 Ignored; included for backward compatibility.
73 Specify specific IP addresses to bind to for TCP and UDP requests.
74 This option may be specified multiple times.
81 Note that when specifying IP addresses with
84 will automatically add
86 and if IPv6 is enabled,
92 requests to be logged.
94 Allow non-root mount requests to be served.
95 This should only be specified if there are clients such as PC's,
97 It will automatically clear the vfs.nfsd.nfs_privport sysctl flag, which
98 controls if the kernel will accept NFS requests from reserved ports only.
102 to bind to the specified port, for both
107 This is typically done to ensure that the port which
109 binds to is a known quantity which can be used in firewall rulesets.
112 cannot bind to this port, an appropriate error will be recorded in
113 the system log, and the daemon will then exit.
115 Do not support the Mount protocol and do not register with
117 This can be done for NFSv4 only servers, since the Mount protocol is not
119 Useful for NFSv4 only servers that do not wish to run
122 will not work, however since NFSv4 mounts are not shown by
124 this should not be an issue for an NFSv4 only server.
126 Allow mount RPCs requests for regular files to be served.
127 Although this seems to violate the mount protocol specification,
128 some diskless workstations do mount requests for
129 their swapfiles and expect them to be regular files.
130 Since a regular file cannot be specified in
132 the entire file system in which the swapfiles resides
133 will have to be exported with the
137 Specify an alternate location
138 for the exports file.
139 More than one exports file can be specified.
141 Tell mountd to suspend/resume execution of the nfsd threads whenever
142 the exports list is being reloaded.
143 This avoids intermittent access
144 errors for clients that do NFS RPCs while the exports are being
145 reloaded, but introduces a delay in RPC response while the reload
149 crashes while an exports load is in progress,
151 must be restarted to get the nfsd threads running again, if this
158 it loads the export host addresses and options into the kernel
162 After changing the exports file,
163 a hangup signal should be sent to the
166 to get it to reload the export information.
167 After sending the SIGHUP
168 (kill \-s HUP `cat /var/run/mountd.pid`),
169 check the syslog output to see if
172 errors in the exports file.
174 If multiple instances of
176 are being run, either in multiple jails or both within
177 and outside of a jail, care must be taken to export
178 any given file system in only one of the instances.
181 jail parameter is required to allow
186 for more information.
190 detects that the running kernel does not include
192 support, it will attempt to load a loadable kernel module containing
201 When run in a jail, the
203 must be done outside the jail, typically by adding
209 file on the jail host.
211 .Bl -tag -width /var/run/mountd.pid -compact
213 the list of exported file systems
214 .It Pa /var/run/mountd.pid
215 the pid of the currently running mountd
216 .It Pa /var/db/mountdtab
217 the current list of remote mounted file systems
232 utility first appeared in