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 May 2, 2006 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.Nm 68will not detach from the controlling terminal and will print 69debugging messages to stderr. 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. 78It will automatically clear the vfs.nfsrv.nfs_privport sysctl flag, which 79controls if the kernel will accept NFS requests from reserved ports only. 80.It Fl p Ar port 81Force 82.Nm 83to bind to the specified port, for both 84.Dv AF_INET 85and 86.Dv AF_INET6 87address families. 88This is typically done to ensure that the port which 89.Nm 90binds to is a known quantity which can be used in firewall rulesets. 91If 92.Nm 93cannot bind to this port, an appropriate error will be recorded in 94the system log, and the daemon will then exit. 95.It Fl r 96Allow mount RPCs requests for regular files to be served. 97Although this seems to violate the mount protocol specification, 98some diskless workstations do mount requests for 99their swapfiles and expect them to be regular files. 100Since a regular file cannot be specified in 101.Pa /etc/exports , 102the entire file system in which the swapfiles resides 103will have to be exported with the 104.Fl alldirs 105flag. 106.It Ar exportsfile 107Specify an alternate location 108for the exports file. 109.El 110.Pp 111When 112.Nm 113is started, 114it loads the export host addresses and options into the kernel 115using the 116.Xr mount 2 117system call. 118After changing the exports file, 119a hangup signal should be sent to the 120.Nm 121daemon 122to get it to reload the export information. 123After sending the SIGHUP 124(kill \-s HUP `cat /var/run/mountd.pid`), 125check the syslog output to see if 126.Nm 127logged any parsing 128errors in the exports file. 129.Pp 130If 131.Nm 132detects that the running kernel does not include 133.Tn NFS 134support, it will attempt to load a loadable kernel module containing 135.Tn NFS 136code, using 137.Xr kldload 2 . 138If this fails, or no 139.Tn NFS 140KLD was available, 141.Nm 142exits with an error. 143.Sh FILES 144.Bl -tag -width /var/run/mountd.pid -compact 145.It Pa /etc/exports 146the list of exported file systems 147.It Pa /var/run/mountd.pid 148the pid of the currently running mountd 149.It Pa /var/db/mountdtab 150the current list of remote mounted file systems 151.El 152.Sh SEE ALSO 153.Xr nfsstat 1 , 154.Xr kldload 2 , 155.Xr exports 5 , 156.Xr nfsd 8 , 157.Xr rpcbind 8 , 158.Xr showmount 8 159.Sh HISTORY 160The 161.Nm 162utility first appeared in 163.Bx 4.4 . 164