xref: /freebsd/usr.sbin/mountd/mountd.8 (revision ce834215a70ff69e7e222827437116eee2f9ac6f)
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.\" 3. All advertising materials mentioning features or use of this software
13.\"    must display the following acknowledgement:
14.\"	This product includes software developed by the University of
15.\"	California, Berkeley and its contributors.
16.\" 4. Neither the name of the University nor the names of its contributors
17.\"    may be used to endorse or promote products derived from this software
18.\"    without specific prior written permission.
19.\"
20.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
21.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
22.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
23.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
24.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
25.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
26.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
27.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
28.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
29.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
30.\" SUCH DAMAGE.
31.\"
32.\"     @(#)mountd.8	8.4 (Berkeley) 4/28/95
33.\"	$Id: mountd.8,v 1.9 1997/04/09 20:25:43 guido Exp $
34.\"
35.Dd April 28, 1995
36.Dt MOUNTD 8
37.Os
38.Sh NAME
39.Nm mountd
40.Nd service remote
41.Tn NFS
42mount requests
43.Sh SYNOPSIS
44.Nm /sbin/mountd
45.Op Fl 2nr
46.Op Ar exportsfile
47.Sh DESCRIPTION
48.Xr Mountd
49is the server for
50.Tn NFS
51mount requests from other client machines.
52.Xr Mountd
53listens for service requests at the port indicated in the
54.Tn NFS
55server specification; see
56.%T "Network File System Protocol Specification" ,
57RFC1094, Appendix A and
58.%T "NFS: Network File System Version 3 Protocol Specification" ,
59Appendix I.
60.Pp
61Options and operands available for
62.Nm mountd :
63.Bl -tag -width Ds
64.It Fl 2
65The
66.Fl 2
67option allows the administrator to force clients to use only the
68version 2 NFS protocol to mount filesystems from this server.
69.It Fl n
70The
71.Fl n
72option allows 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.nfs.nfs_privport sysctl flag, which
76controls if the kernel will accept nfs requests form reserved ports only.
77.It Fl r
78The
79.Fl r
80option allows mount RPCs requests for regular files to be served.
81Although this seems to violate the mount protocol specification,
82some diskless workstations do mount requests for
83their swapfiles and expect them to be regular files.
84Since a regular file cannot be specified in
85.Pa /etc/exports ,
86the entire file system in which the swapfiles resides
87will have to be exported with the
88.Fl alldirs
89flag.
90.It Ar exportsfile
91The
92.Ar exportsfile
93argument specifies an alternate location
94for the exports file.
95.El
96.Pp
97When mountd is started,
98it loads the export host addresses and options into the kernel
99using the mount(2) system call.
100After changing the exports file,
101a hangup signal should be sent to the mountd daemon
102to get it to reload the export information.
103After sending the SIGHUP
104(kill \-s HUP `cat /var/run/mountd.pid`),
105check the syslog output to see if mountd logged any parsing
106errors in the exports file.
107.Pp
108If
109.Nm mountd
110detects that the running kernel does not include
111.Tn NFS
112support, it will attempt to load a loadable kernel module containing
113.Tn NFS
114code, using
115.Xr modload 8
116by way of
117.Xr vfsload 3 .
118If this fails, or no
119.Tn NFS
120LKM was available,
121.Nm mountd
122exits with an error.
123.Sh FILES
124.Bl -tag -width /var/run/mountd.pid -compact
125.It Pa /etc/exports
126the list of exported filesystems
127.It Pa /var/run/mountd.pid
128the pid of the currently running mountd
129.It Pa /var/db/mountdtab
130the current list of remote mounted filesystems
131.El
132.Sh SEE ALSO
133.Xr nfsstat 1 ,
134.Xr exports 5 ,
135.Xr modload 8 ,
136.Xr nfsd 8 ,
137.Xr portmap 8 ,
138.Xr showmount 8
139.Sh HISTORY
140The
141.Nm mountd
142utility first appeared in
143.Bx 4.4 .
144