exports.5 (223954) | exports.5 (233648) |
---|---|
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. --- 12 unchanged lines hidden (view full) --- 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.\" @(#)exports.5 8.3 (Berkeley) 3/29/95 | 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. --- 12 unchanged lines hidden (view full) --- 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.\" @(#)exports.5 8.3 (Berkeley) 3/29/95 |
29.\" $FreeBSD: head/usr.sbin/mountd/exports.5 223954 2011-07-12 14:04:36Z rmacklem $ | 29.\" $FreeBSD: head/usr.sbin/mountd/exports.5 233648 2012-03-29 05:02:12Z eadler $ |
30.\" 31.Dd July 12, 2011 32.Dt EXPORTS 5 33.Os 34.Sh NAME 35.Nm exports 36.Nd define remote mount points for 37.Tn NFS --- 30 unchanged lines hidden (view full) --- 68.Pp 69In a mount entry, 70the first field(s) specify the directory path(s) within a server file system 71that can be mounted on by the corresponding client(s). 72There are three forms of this specification. 73The first is to list all mount points as absolute 74directory paths separated by whitespace. 75This list of directory paths should be considered an | 30.\" 31.Dd July 12, 2011 32.Dt EXPORTS 5 33.Os 34.Sh NAME 35.Nm exports 36.Nd define remote mount points for 37.Tn NFS --- 30 unchanged lines hidden (view full) --- 68.Pp 69In a mount entry, 70the first field(s) specify the directory path(s) within a server file system 71that can be mounted on by the corresponding client(s). 72There are three forms of this specification. 73The first is to list all mount points as absolute 74directory paths separated by whitespace. 75This list of directory paths should be considered an |
76.Dq administrative control , | 76.Dq administrative control , |
77since it is only enforced by the 78.Xr mountd 8 79daemon and not the kernel. 80As such, it only applies to NFSv2 and NFSv3 mounts and only 81with respect to the client's use of the mount protocol. 82The second is to specify the pathname of the root of the file system 83followed by the 84.Fl alldirs 85flag; 86this form allows the host(s) to mount at any point within the file system, 87including regular files if the 88.Fl r 89option is used on 90.Xr mountd 8 . 91Because NFSv4 does not use the mount protocol, 92the | 77since it is only enforced by the 78.Xr mountd 8 79daemon and not the kernel. 80As such, it only applies to NFSv2 and NFSv3 mounts and only 81with respect to the client's use of the mount protocol. 82The second is to specify the pathname of the root of the file system 83followed by the 84.Fl alldirs 85flag; 86this form allows the host(s) to mount at any point within the file system, 87including regular files if the 88.Fl r 89option is used on 90.Xr mountd 8 . 91Because NFSv4 does not use the mount protocol, 92the |
93.Dq administrative controls | 93.Dq administrative controls |
94are not applied. 95Thus, all the above export line(s) should be considered to have the 96.Fl alldirs 97flag, even if the line is specified without it. 98The third form has the string ``V4:'' followed by a single absolute path 99name, to specify the NFSv4 tree root. 100This line does not export any file system, but simply marks where the root 101of the server's directory tree is for NFSv4 clients. --- 408 unchanged lines hidden --- | 94are not applied. 95Thus, all the above export line(s) should be considered to have the 96.Fl alldirs 97flag, even if the line is specified without it. 98The third form has the string ``V4:'' followed by a single absolute path 99name, to specify the NFSv4 tree root. 100This line does not export any file system, but simply marks where the root 101of the server's directory tree is for NFSv4 clients. --- 408 unchanged lines hidden --- |