From 65518c708920436ded6d9a56931d8228a77dc0b8 Mon Sep 17 00:00:00 2001 From: Ben Smithurst Date: Sun, 31 Dec 2000 03:18:35 +0000 Subject: [PATCH] Add a question and answer about mountd complaining about bad exports lists. (Slightly modified from the patch in the PR, I changed a to a
as it seemed more appropriate.) PR: 23950 Submitted by: Dima Dorfman , Crist J. Clark --- en_US.ISO8859-1/books/faq/book.sgml | 65 +++++++++++++++++++++++++++- en_US.ISO_8859-1/books/faq/book.sgml | 65 +++++++++++++++++++++++++++- 2 files changed, 128 insertions(+), 2 deletions(-) diff --git a/en_US.ISO8859-1/books/faq/book.sgml b/en_US.ISO8859-1/books/faq/book.sgml index 78d5d31cb7..890239af6b 100644 --- a/en_US.ISO8859-1/books/faq/book.sgml +++ b/en_US.ISO8859-1/books/faq/book.sgml @@ -15,7 +15,7 @@ - $FreeBSD$ + $FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.130 2000/12/29 15:17:20 phantom Exp $ This is the FAQ for FreeBSD versions 2.X, 3.X, and 4.X. @@ -7699,6 +7699,69 @@ Key F15 A A Menu Workplace Nop + + + Why does mountd keep telling me it + can't change attributes and that I have a + bad exports list on my FreeBSD NFS + server? + + + + The most frequent problem is not understanding this + passage from the &man.exports.5 manual page + correctly: + +
+ Each line in the file (other than comment + lines that begin with a #) specifies the mount point(s) + and export flags within one local server filesystem for + one or more hosts. A host may be specified only once + for each local filesystem on the server and there may be + only one default entry for each server filesystem that + applies to all other hosts. +
+ + This is made more clear by an example of a common + mistake. If everything above /usr is + part of one filesystem (there are no mounts above + /usr) the following exports list is + not valid: + + /usr/src client +/usr/ports client + + There are two lines specifying properties for one + filesystem, /usr, exported to the + same host, client. The correct format + is: + + /usr/src /usr/ports client + + To rephrase the passage from the manual page, the + properties of one filesystem exported to a given host + (world-wide exports are treated like another unique host) + must all occur on one line. And yes, this does cause + limitiation in how you can export filesystems without ugly + workarounds, but for most people, this is not an + issue. + + The following is an example of a valid export list, + where /usr and + /exports are local + filesystems: + + # Export src and ports to client01 and client02, but only +# client01 has root privileges on it +/usr/src /usr/ports -maproot=0 client01 +/usr/src /usr/ports client02 +# The "client" machines have root and can mount anywhere +# up /exports. The world can mount /exports/obj read-only +/exports -alldirs -maproot=0 client01 client02 +/exports/obj -ro + + + I'm having problems talking PPP to NeXTStep diff --git a/en_US.ISO_8859-1/books/faq/book.sgml b/en_US.ISO_8859-1/books/faq/book.sgml index 78d5d31cb7..890239af6b 100644 --- a/en_US.ISO_8859-1/books/faq/book.sgml +++ b/en_US.ISO_8859-1/books/faq/book.sgml @@ -15,7 +15,7 @@ - $FreeBSD$ + $FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.130 2000/12/29 15:17:20 phantom Exp $ This is the FAQ for FreeBSD versions 2.X, 3.X, and 4.X. @@ -7699,6 +7699,69 @@ Key F15 A A Menu Workplace Nop + + + Why does mountd keep telling me it + can't change attributes and that I have a + bad exports list on my FreeBSD NFS + server? + + + + The most frequent problem is not understanding this + passage from the &man.exports.5 manual page + correctly: + +
+ Each line in the file (other than comment + lines that begin with a #) specifies the mount point(s) + and export flags within one local server filesystem for + one or more hosts. A host may be specified only once + for each local filesystem on the server and there may be + only one default entry for each server filesystem that + applies to all other hosts. +
+ + This is made more clear by an example of a common + mistake. If everything above /usr is + part of one filesystem (there are no mounts above + /usr) the following exports list is + not valid: + + /usr/src client +/usr/ports client + + There are two lines specifying properties for one + filesystem, /usr, exported to the + same host, client. The correct format + is: + + /usr/src /usr/ports client + + To rephrase the passage from the manual page, the + properties of one filesystem exported to a given host + (world-wide exports are treated like another unique host) + must all occur on one line. And yes, this does cause + limitiation in how you can export filesystems without ugly + workarounds, but for most people, this is not an + issue. + + The following is an example of a valid export list, + where /usr and + /exports are local + filesystems: + + # Export src and ports to client01 and client02, but only +# client01 has root privileges on it +/usr/src /usr/ports -maproot=0 client01 +/usr/src /usr/ports client02 +# The "client" machines have root and can mount anywhere +# up /exports. The world can mount /exports/obj read-only +/exports -alldirs -maproot=0 client01 client02 +/exports/obj -ro + + + I'm having problems talking PPP to NeXTStep