fsfacca@AVELON.LERC.NASA.GOV (Tony Facca) (06/30/90)
I have a question regarding exporting file systems with the -root[id] option.
On the Iris 4D's I have an /etc/exports file which looks something like this:
#
# NFS exported filesystem database (see EXPORTS(4) for more information).
#
# Entries in this file consist of lines containing the following fields:
#
# filesystem [ options ] [ netgroup ] [ hostname ] ...
#
# Filesystem must be left-justified and may name any directory within a
# local filesystem. Lines beginning with white space continue the previous
# line's entry. Netgroup(4) and hostname refer to machines or collections
# of machines to which filesystem is exported.
#
/usr/lerc -root=lerc08:lerc09,access=lerc02:lerc03:lerc04:lerc08:lerc09
This works the way I want it to. That is, if I mount the /usr/lerc directory
from lerc08 I can be root in the mounted directory.
I am trying to duplicate this effect on the 3030's. There is no "root" option
but there is a "rootid" option which allows one to specify a userid to map
client "root" ids to. Like, rootid=guest would change the permissions of the
remote root to guest on the server.
I want to map root to root, but only on a subset of the machines to which I
grant access. I have tried variations on this theme:
------
# Iris 3030's /etc/exports
/u/lerc -rootid=root lerc08 lerc09
/u/lerc lerc02 lerc03 lerc04 lerc08 lerc09 lerc10
------
Has anyone successfully exported file systems on the 3030's using a scheme like
this? Any help is appreciated.
On another note...
The header for the /etc/exports file on the 4D's reads "Lines beginning with
white space continue the previous line's entry." Yet when I try to set up an
exports file like this:
/usr/lerc -root=lerc08:lerc09,
access=lerc02:lerc03:lerc04:
lerc08:lerc09:lerc10
Doing an exportfs gives me errors:
#exportfs -a
exportfs: access=lerc02:lerc03:lerc04:: No such file or directory
exportfs: lerc08:lerc09:lerc10: No such file or directory
So, what exactly does the comment about "Lines beginning with white space.."
mean?
--
-----------------------------------------------------------------------------
Tony Facca | fsfacca@avelon.lerc.nasa.gov | phone: 216-433-8318
-----------------------------------------------------------------------------
You are at Witt's end. Passages lead off in *all* directions.blbates@AERO4.LARC.NASA.GOV ("Brent L. Bates AAD/TAB MS361 x42854") (06/30/90)
On lines beginning with white space, is your `white space' spaces " " or tab characters. I know somethings expect a tab and a space will not work. -- Brent L. Bates NASA-Langley Research Center M.S. 361 Hampton, Virginia 23665-5225 (804) 864-2854 E-mail: blbates@aero4.larc.nasa.gov or blbates@aero2.larc.nasa.gov
brendan@nimrod.wpd.sgi.com (Brendan Eich) (06/30/90)
In article <9006291911.AA25941@avelon.lerc.nasa.gov>, fsfacca@AVELON.LERC.NASA.GOV (Tony Facca) writes: > > I have a question regarding exporting file systems with the -root[id] option. > On the Iris 4D's I have an /etc/exports file which looks something like this: > > /usr/lerc -root=lerc08:lerc09,access=lerc02:lerc03:lerc04:lerc08:lerc09 > > This works the way I want it to. That is, if I mount the /usr/lerc directory > from lerc08 I can be root in the mounted directory. > > I am trying to duplicate this effect on the 3030's. There is no "root" option > but there is a "rootid" option which allows one to specify a userid to map > client "root" ids to. Like, rootid=guest would change the permissions of the > remote root to guest on the server. The -rootid option was SGI's best guess and first implementation of what Sun later called the -anon option (we implemented a root-uid-mapping option before they did, based on incomplete hooks in their NFSSRC3.0 release). The last release for the 3000 series, 3.6, was released a year before SGI integrated exportfs and the -root option from Sun's DNFS1.0 source release. The -root, -rw= (read-mostly), and -anon (synonymous with -rootid for SGI) options are therefore available only on the 4D series. > So, what exactly does the comment about "Lines beginning with white space.." > mean? The comment lies. To continue a long logical line across several physical lines, end each line but the last with a backslash ('\'). Brendan