xref: /freebsd/usr.sbin/mountd/mountd.8 (revision 486c8cc4c6cb7a6077c0598a04262be512749b36)
1.\" Copyright (c) 1989, 1991, 1993
2.\"	The Regents of the University of California.  All rights reserved.
3.\"
4.\" Redistribution and use in source and binary forms, with or without
5.\" modification, are permitted provided that the following conditions
6.\" are met:
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.\" 4. 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.
15.\"
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
26.\" SUCH DAMAGE.
27.\"
28.\"     @(#)mountd.8	8.4 (Berkeley) 4/28/95
29.\" $FreeBSD$
30.\"
31.Dd April 28, 1995
32.Dt MOUNTD 8
33.Os
34.Sh NAME
35.Nm mountd
36.Nd service remote
37.Tn NFS
38mount requests
39.Sh SYNOPSIS
40.Nm
41.Op Fl 2dlnr
42.Op Fl p Ar port
43.Op Ar exportsfile
44.Sh DESCRIPTION
45The
46.Nm
47utility is the server for
48.Tn NFS
49mount requests from other client machines.
50It listens for service requests at the port indicated in the
51.Tn NFS
52server specification; see
53.%T "Network File System Protocol Specification" ,
54RFC1094, Appendix A and
55.%T "NFS: Network File System Version 3 Protocol Specification" ,
56Appendix I.
57.Pp
58The following options are available:
59.Bl -tag -width indent
60.It Fl 2
61Allow the administrator to force clients to use only the
62version 2
63.Tn NFS
64protocol to mount file systems from this server.
65.It Fl d
66Output debugging information.
67.It Fl l
68Cause all succeeded
69.Nm
70requests to be logged.
71.It Fl n
72Allow non-root mount requests to be served.
73This should only be specified if there are clients such as PC's,
74that require it.
75It will automatically clear the vfs.nfsrv.nfs_privport sysctl flag, which
76controls if the kernel will accept NFS requests from reserved ports only.
77.It Fl p Ar port
78Force
79.Nm
80to bind to the specified port, for both
81.Dv AF_INET
82and
83.Dv AF_INET6
84address families.
85This is typically done to ensure that the port which
86.Nm
87binds to is a known quantity which can be used in firewall rulesets.
88If
89.Nm
90cannot bind to this port, an appropriate error will be recorded in
91the system log, and the daemon will then exit.
92.It Fl r
93Allow mount RPCs requests for regular files to be served.
94Although this seems to violate the mount protocol specification,
95some diskless workstations do mount requests for
96their swapfiles and expect them to be regular files.
97Since a regular file cannot be specified in
98.Pa /etc/exports ,
99the entire file system in which the swapfiles resides
100will have to be exported with the
101.Fl alldirs
102flag.
103.It Ar exportsfile
104Specify an alternate location
105for the exports file.
106.El
107.Pp
108When
109.Nm
110is started,
111it loads the export host addresses and options into the kernel
112using the
113.Xr mount 2
114system call.
115After changing the exports file,
116a hangup signal should be sent to the
117.Nm
118daemon
119to get it to reload the export information.
120After sending the SIGHUP
121(kill \-s HUP `cat /var/run/mountd.pid`),
122check the syslog output to see if
123.Nm
124logged any parsing
125errors in the exports file.
126.Pp
127If
128.Nm
129detects that the running kernel does not include
130.Tn NFS
131support, it will attempt to load a loadable kernel module containing
132.Tn NFS
133code, using
134.Xr kldload 2 .
135If this fails, or no
136.Tn NFS
137KLD was available,
138.Nm
139exits with an error.
140.Sh FILES
141.Bl -tag -width /var/run/mountd.pid -compact
142.It Pa /etc/exports
143the list of exported file systems
144.It Pa /var/run/mountd.pid
145the pid of the currently running mountd
146.It Pa /var/db/mountdtab
147the current list of remote mounted file systems
148.El
149.Sh SEE ALSO
150.Xr nfsstat 1 ,
151.Xr kldload 2 ,
152.Xr exports 5 ,
153.Xr nfsd 8 ,
154.Xr rpcbind 8 ,
155.Xr showmount 8
156.Sh HISTORY
157The
158.Nm
159utility first appeared in
160.Bx 4.4 .
161