xref: /netbsd-src/usr.sbin/mountd/mountd.8 (revision bbde328be4e75ea9ad02e9715ea13ca54b797ada)
1.\"	$NetBSD: mountd.8,v 1.32 2006/01/05 10:41:03 yamt Exp $
2.\"
3.\" Copyright (c) 1989, 1991, 1993
4.\"	The Regents of the University of California.  All rights reserved.
5.\"
6.\" Redistribution and use in source and binary forms, with or without
7.\" modification, are permitted provided that the following conditions
8.\" are met:
9.\" 1. Redistributions of source code must retain the above copyright
10.\"    notice, this list of conditions and the following disclaimer.
11.\" 2. Redistributions in binary form must reproduce the above copyright
12.\"    notice, this list of conditions and the following disclaimer in the
13.\"    documentation and/or other materials provided with the distribution.
14.\" 3. Neither the name of the University nor the names of its contributors
15.\"    may be used to endorse or promote products derived from this software
16.\"    without specific prior written permission.
17.\"
18.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
19.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
20.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
21.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
22.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
23.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
24.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
25.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
26.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
27.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
28.\" SUCH DAMAGE.
29.\"
30.\"     @(#)mountd.8	8.4 (Berkeley) 4/28/95
31.\"
32.Dd January 5, 2006
33.Dt MOUNTD 8
34.Os
35.Sh NAME
36.Nm mountd
37.Nd service remote
38.Tn NFS
39mount requests
40.Sh SYNOPSIS
41.Nm
42.Op Fl dNn
43.Op Fl P Ar policy
44.Op Fl p Ar port
45.Op Ar exportsfile
46.Sh DESCRIPTION
47.Nm
48is the server for
49.Tn NFS
50mount requests from other client machines.
51.Nm
52listens for service requests at the port indicated in the
53.Tn NFS
54server specification; see
55.%T "Network File System Protocol Specification" ,
56RFC 1094, Appendix A and
57.%T "NFS: Network File System Version 3 Protocol Specification" ,
58Appendix I.
59.Pp
60Options and operands available for
61.Nm mountd :
62.Bl -tag -width Ds
63.It Fl d
64Enable debugging mode.
65.Nm
66will not detach from the controlling terminal and will print
67debugging messages to stderr.
68.It Fl N
69Do not require privileged ports for mount or NFS RPC calls.
70This option is equivalent to specifying
71.Dq -noresvport -noresvmnt
72on every export.
73See
74.Xr exports 5
75for more information.
76.It Fl n
77This flag used to indicate that clients were required to make requests
78from reserved ports, but it is now no longer functional. It
79is only provided for backwards compatibility. Requests
80are checked for reserved ports on a per-export basis, see
81.Xr exports 5 .
82.It Fl P Ar policy
83IPsec
84.Ar policy
85string,
86as described in
87.Xr ipsec_set_policy 3 .
88Multiple IPsec policy strings may be specified by using a semicolon as
89a separator. If conflicting policy strings are found in a single line,
90the last string will take effect. If an invalid IPsec policy string is used
91.Nm
92logs an error message and terminates itself.
93.It Fl p Ar port
94Force
95.Nm
96to bind to the given port. If this
97option is not given,
98.Nm
99may bind to every anonymous port
100(in the range 600-1023) which causes trouble when trying to use
101NFS through a firewall.
102.It Ar exportsfile
103The
104.Ar exportsfile
105argument specifies an alternative location
106for the exports file.
107.El
108.Pp
109When
110.Nm
111is started,
112it loads the export host addresses and options into the kernel
113using the
114.Xr nfssvc 2
115system call.
116After changing the exports file,
117a hangup signal should be sent to the
118.Nm
119daemon to 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 errors in the exports file.
125.Pp
126After receiving SIGTERM,
127.Nm
128sends a broadcast request to remove the mount list from all the clients.
129This can take a long time, since the broadcast request waits for each
130client to respond.
131.Sh FILES
132.Bl -tag -width /var/run/mountd.pid -compact
133.It Pa /etc/exports
134the list of exported filesystems
135.It Pa /var/run/mountd.pid
136the pid of the currently running
137.Nm
138.It Pa /var/db/mountdtab
139the list of remotely mounted filesystems
140.El
141.Sh SEE ALSO
142.Xr nfsstat 1 ,
143.Xr nfssvc 2 ,
144.Xr exports 5 ,
145.Xr nfsd 8 ,
146.Xr rpcbind 8 ,
147.Xr showmount 8
148.Sh HISTORY
149The
150.Nm
151utility first appeared in
152.Bx 4.4 .
153