Numerous adjustments to the recent rpcbind etc. changes.
[dragonfly.git] / sbin / mountd / mountd.8
CommitLineData
984263bc
MD
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.\" $FreeBSD: src/sbin/mountd/mountd.8,v 1.16.2.2 2000/12/08 14:04:02 ru Exp $
62f7f702 34.\" $DragonFly: src/sbin/mountd/mountd.8,v 1.5 2008/05/09 20:31:04 swildner Exp $
984263bc
MD
35.\"
36.Dd April 28, 1995
37.Dt MOUNTD 8
38.Os
39.Sh NAME
40.Nm mountd
41.Nd service remote
42.Tn NFS
43mount requests
44.Sh SYNOPSIS
45.Nm
46.Op Fl 2dlnr
47.Op Ar exportsfile
48.Sh DESCRIPTION
49.Nm Mountd
50is the server for
51.Tn NFS
52mount requests from other client machines.
53It listens for service requests at the port indicated in the
54.Tn NFS
55server specification; see
56.%T "Network File System Protocol Specification" ,
cabeba47 57RFC 1094, Appendix A and
984263bc
MD
58.%T "NFS: Network File System Version 3 Protocol Specification" ,
59Appendix I.
60.Pp
61The following options are available:
62.Bl -tag -width indent
63.It Fl 2
64Allow the administrator to force clients to use only the
65version 2
66.Tn NFS
67protocol to mount filesystems from this server.
68.It Fl d
69Output debugging information.
70.It Fl l
71Cause all succeeded
72.Nm
73requests to be logged.
74.It Fl n
75Allow non-root mount requests to be served.
76This should only be specified if there are clients such as PC's,
77that require it.
e9c76aaf
SW
78It will automatically clear the
79.Va vfs.nfs.nfs_privport
80sysctl flag, which
984263bc
MD
81controls if the kernel will accept NFS requests from reserved ports only.
82.It Fl r
83Allow mount RPCs requests for regular files to be served.
84Although this seems to violate the mount protocol specification,
85some diskless workstations do mount requests for
86their swapfiles and expect them to be regular files.
87Since a regular file cannot be specified in
88.Pa /etc/exports ,
89the entire file system in which the swapfiles resides
90will have to be exported with the
91.Fl alldirs
92flag.
93.It Ar exportsfile
94Specify an alternate location
95for the exports file.
96.El
97.Pp
98When
99.Nm
100is started,
101it loads the export host addresses and options into the kernel
102using the
103.Xr mount 2
104system call.
105After changing the exports file,
106a hangup signal should be sent to the
107.Nm
108daemon
109to get it to reload the export information.
62f7f702
SW
110After sending the
111.Dv SIGHUP
984263bc
MD
112(kill \-s HUP `cat /var/run/mountd.pid`),
113check the syslog output to see if
114.Nm
115logged any parsing
116errors in the exports file.
117.Pp
118If
119.Nm
120detects that the running kernel does not include
121.Tn NFS
122support, it will attempt to load a loadable kernel module containing
123.Tn NFS
124code, using
125.Xr kldload 8
126by way of
127.Xr vfsload 3 .
128If this fails, or no
129.Tn NFS
130KLD was available,
131.Nm
132exits with an error.
133.Sh FILES
134.Bl -tag -width /var/run/mountd.pid -compact
135.It Pa /etc/exports
136the list of exported filesystems
137.It Pa /var/run/mountd.pid
138the pid of the currently running mountd
139.It Pa /var/db/mountdtab
140the current list of remote mounted filesystems
141.El
142.Sh SEE ALSO
143.Xr nfsstat 1 ,
144.Xr exports 5 ,
145.Xr kldload 8 ,
146.Xr nfsd 8 ,
3b813696 147.Xr rpcbind 8 ,
984263bc
MD
148.Xr showmount 8
149.Sh HISTORY
150The
151.Nm
152utility first appeared in
153.Bx 4.4 .