|
Lines 7701-7706
Link Here
|
| 7701 |
</qandaentry> |
7701 |
</qandaentry> |
| 7702 |
|
7702 |
|
| 7703 |
<qandaentry> |
7703 |
<qandaentry> |
|
|
7704 |
<question id="exports-errors"> |
| 7705 |
<para>Why does <command>mountd</command> keep telling me it |
| 7706 |
<quote>can't change attributes</quote> and that I have a |
| 7707 |
<quote>bad exports list</quote> on my FreeBSD NFS |
| 7708 |
server?</para> |
| 7709 |
</question> |
| 7710 |
|
| 7711 |
<answer> |
| 7712 |
<para>The most frequent problem is not understanding this |
| 7713 |
passage from the &man.exports.5 manual page |
| 7714 |
correctly:</para> |
| 7715 |
|
| 7716 |
<programlisting>Each line in the file (other than comment lines that begin with a #) |
| 7717 |
specifies the mount point(s) and export flags within one local server |
| 7718 |
filesystem for one or more hosts. A host may be specified only once |
| 7719 |
for each local filesystem on the server and there may be only one |
| 7720 |
default entry for each server filesystem that applies to all other |
| 7721 |
hosts.</programlisting> |
| 7722 |
|
| 7723 |
<para>This is made more clear by an example of a common |
| 7724 |
mistake. If everything above <filename>/usr</filename> is |
| 7725 |
part of one filesystem (there are no mounts above |
| 7726 |
<filename>/usr</filename>) the following exports list is |
| 7727 |
not valid:</para> |
| 7728 |
|
| 7729 |
<programlisting>/usr/src client |
| 7730 |
/usr/ports client</programlisting> |
| 7731 |
|
| 7732 |
<para>There are two lines specifying properties for one |
| 7733 |
filesystem, <filename>/usr</filename>, exported to the |
| 7734 |
same host, <hostid>client</hostid>. The correct format |
| 7735 |
is:</para> |
| 7736 |
|
| 7737 |
<programlisting>/usr/src /usr/ports client</programlisting> |
| 7738 |
|
| 7739 |
<para>To rephrase the passage from the manual page, the |
| 7740 |
properties of one filesystem exported to a given host |
| 7741 |
(world-wide exports are treated like another unique host) |
| 7742 |
must all occur on one line. And yes, this does cause |
| 7743 |
limitiation in how you can export filesystems without ugly |
| 7744 |
workarounds, but for most people, this is not an |
| 7745 |
issue.</para> |
| 7746 |
|
| 7747 |
<para>The following is an example of a valid export list, |
| 7748 |
where <filename>/usr</filename> and |
| 7749 |
<filename>/exports</filename> are local |
| 7750 |
filesystems:</para> |
| 7751 |
|
| 7752 |
<programlisting># Export src and ports to client01 and client02, but only |
| 7753 |
# client01 has root privileges on it |
| 7754 |
/usr/src /usr/ports -maproot=0 client01 |
| 7755 |
/usr/src /usr/ports client02 |
| 7756 |
# The "client" machines have root and can mount anywhere |
| 7757 |
# up /exports. The world can mount /exports/obj read-only |
| 7758 |
/exports -alldirs -maproot=0 client01 client02 |
| 7759 |
/exports/obj -ro</programlisting> |
| 7760 |
</answer> |
| 7761 |
</qandaentry> |
| 7762 |
|
| 7763 |
<qandaentry> |
| 7704 |
<question id="ppp-nextstep"> |
7764 |
<question id="ppp-nextstep"> |
| 7705 |
<para>I'm having problems talking PPP to NeXTStep |
7765 |
<para>I'm having problems talking PPP to NeXTStep |
| 7706 |
machines.</para> |
7766 |
machines.</para> |