mccalpin@MASIG1.OCEAN.FSU.EDU ("John D. McCalpin") (10/28/88)
Background: running 3.6 NFS on IRIS 3000 machines
Is it possible to have a file system exported on a read-only basis
to some nodes and read-write to others?
I want to allow my own IRIS's to cross-mount with read/write access,
and I want another (limited) group of semi-trusted hosts to be able to
mount some of my filesystems read-only.
If it is possible, could someone tell me the proper syntax for the
/etc/exports entries?
Every time I have tried to put multiple entries in /etc/exports
for a single file system, it has caused the remote system to become
seriously confused. I have had to change the exports file back to its
original state and reboot.
----------------------------------------------------------------
John D. McCalpin
Mesoscale Air-Sea Interaction Group &
Department of Oceanography &
Supercomputer Computations Research Institute
The Florida State University
mccalpin@masig1.ocean.fsu.edu (requires nameserver to access)
mccalpin@nu.cs.fsu.edu (in DOD host tables)
mccalpin@fsu (BITNET or MFENET)
SCRI::MCCALPIN (SPAN)
----------------------------------------------------------------rpaul@dasys1.UUCP (Rod Paul) (10/29/88)
I beleive the entries go somewhat like this: partition client client -read check the manual for correct syntax
root@tread.SGI.COM (0000-Admin(0000)) (11/02/88)
Yes, it is possible to have a file system exported on a read-only basis
to some nodes and read-write to others, but not in SGI release 3.6 for the
3000 series. This enhancement to exporting did not appear until Sun's 4.0
release and SGI's 4D3.1 release.
The new /etc/exports format allows you to specify:
/usr/src -rw=hostA:hostB:hostC
which gives hostA, hostB, and hostC read-write access to the server's
/usr/src tree and read-only access to everyone else. See exports(4),
rw= option, and exportfs(1M).
It should be noted that using multiple entries for a given file system in
/etc/exports in an attempt to export to different clients with different
options is not supported. If you'd like more detailed information as to
what is going on, you can look at /usr/adm/syslog which is where mountd
reports its problems.
Dana Treadwell