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 October 20, 2007 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 h Ar bindip 43.Op Fl p Ar port 44.Op Ar exportsfile ... 45.Sh DESCRIPTION 46The 47.Nm 48utility is the server for 49.Tn NFS 50mount requests from other client machines. 51It listens for service requests at the port indicated in the 52.Tn NFS 53server specification; see 54.%T "Network File System Protocol Specification" , 55RFC1094, Appendix A and 56.%T "NFS: Network File System Version 3 Protocol Specification" , 57Appendix I. 58.Pp 59The following options are available: 60.Bl -tag -width indent 61.It Fl 2 62Allow the administrator to force clients to use only the 63version 2 64.Tn NFS 65protocol to mount file systems from this server. 66.It Fl d 67Output debugging information. 68.Nm 69will not detach from the controlling terminal and will print 70debugging messages to stderr. 71.It Fl h Ar bindip 72Specify specific IP addresses to bind to for TCP and UDP requests. 73This option may be specified multiple times. 74If no 75.Fl h 76option is specified, 77.Nm 78will bind to 79.Dv INADDR_ANY . 80Note that when specifying IP addresses with 81.Fl h , 82.Nm 83will automatically add 84.Li 127.0.0.1 85and if IPv6 is enabled, 86.Li ::1 87to the list. 88.It Fl l 89Cause all succeeded 90.Nm 91requests to be logged. 92.It Fl n 93Allow non-root mount requests to be served. 94This should only be specified if there are clients such as PC's, 95that require it. 96It will automatically clear the vfs.nfsrv.nfs_privport sysctl flag, which 97controls if the kernel will accept NFS requests from reserved ports only. 98.It Fl p Ar port 99Force 100.Nm 101to bind to the specified port, for both 102.Dv AF_INET 103and 104.Dv AF_INET6 105address families. 106This is typically done to ensure that the port which 107.Nm 108binds to is a known quantity which can be used in firewall rulesets. 109If 110.Nm 111cannot bind to this port, an appropriate error will be recorded in 112the system log, and the daemon will then exit. 113.It Fl r 114Allow mount RPCs requests for regular files to be served. 115Although this seems to violate the mount protocol specification, 116some diskless workstations do mount requests for 117their swapfiles and expect them to be regular files. 118Since a regular file cannot be specified in 119.Pa /etc/exports , 120the entire file system in which the swapfiles resides 121will have to be exported with the 122.Fl alldirs 123flag. 124.It Ar exportsfile 125Specify an alternate location 126for the exports file. 127More than one exports file can be specified. 128.El 129.Pp 130When 131.Nm 132is started, 133it loads the export host addresses and options into the kernel 134using the 135.Xr mount 2 136system call. 137After changing the exports file, 138a hangup signal should be sent to the 139.Nm 140daemon 141to get it to reload the export information. 142After sending the SIGHUP 143(kill \-s HUP `cat /var/run/mountd.pid`), 144check the syslog output to see if 145.Nm 146logged any parsing 147errors in the exports file. 148.Pp 149If 150.Nm 151detects that the running kernel does not include 152.Tn NFS 153support, it will attempt to load a loadable kernel module containing 154.Tn NFS 155code, using 156.Xr kldload 2 . 157If this fails, or no 158.Tn NFS 159KLD was available, 160.Nm 161exits with an error. 162.Sh FILES 163.Bl -tag -width /var/run/mountd.pid -compact 164.It Pa /etc/exports 165the list of exported file systems 166.It Pa /var/run/mountd.pid 167the pid of the currently running mountd 168.It Pa /var/db/mountdtab 169the current list of remote mounted file systems 170.El 171.Sh SEE ALSO 172.Xr nfsstat 1 , 173.Xr kldload 2 , 174.Xr exports 5 , 175.Xr nfsd 8 , 176.Xr rpcbind 8 , 177.Xr showmount 8 178.Sh HISTORY 179The 180.Nm 181utility first appeared in 182.Bx 4.4 . 183