[ale] weird nfs problem
Dow Hurst
dhurst at kennesaw.edu
Thu Feb 13 15:33:49 EST 2003
In fact, here is an example from my SGI /etc/exports file. The syntax
may be a bit different under Linux.
# 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. A backslash (\) at the end of a line permits splitting
# long lines into shorter ones. Netgroup(4) and hostname refer
# to machines or collections of machines to which filesystem is exported.
#
/d2 -rw=Cedric.kennesaw.edu:Erkki.kennesaw.edu:Aslan.kennesaw.edu:\
Per.kennesaw.edu:Methane.kennesaw.edu:Ethane.kennesaw.edu:\
Heptane.kennesaw.edu:Octane.kennesaw.edu:Raven.kennesaw.edu:\
Hughes1.kennesaw.edu:Fluffy.kennesaw.edu:Knife.kennesaw.edu \
Cedric.kennesaw.edu:Erkki.kennesaw.edu:Aslan.kennesaw.edu\
Per.kennesaw.edu:Methane.kennesaw.edu:Ethane.kennesaw.edu\
Heptane.kennesaw.edu:Octane.kennesaw.edu:Raven.kennesaw.edu\
Hughes1.kennesaw.edu:Fluffy.kennesaw.edu:Knife.kennesaw.edu
You'll probably have to watch the line wrap. I found that wrapping
lines with the backslash worked well for me. The FQDN was important to
include since my /etc/hosts entries were passed over the network for
authentication as FQDNs. The second set of entries is actually the
-access= keyword in an implicit format. Other OSes than IRIX may have a
different syntax. Bob Toxen passed on to me that even though Sun has
published the standards for NFS, almost every server and client he has
dealt with treats the standards in their own special way. :-)
Here is an example /etc/fstab:
/dev/root / xfs rw,raw=/dev/rroot 0 0
#
#NFS Mounts
walker:/d3 /nfs/walker.d3 nfs rw,hard,intr,bg,nosuid 0 0
raven:/d2 /nfs/raven nfs rw,hard,intr,bg,nosuid 0 0
per:/d2 /nfs/per nfs rw,hard,intr,bg,nosuid 0 0
hughes1:/d2 /nfs/hughes1 nfs rw,hard,intr,bg,nosuid 0 0
benzene:/d2 /nfs/benzene nfs rw,hard,intr,bg,nosuid 0 0
aslan:/d2 /nfs/aslan nfs rw,hard,intr,bg,nosuid,vers=2 0 0
linus:/d2 /nfs/linus nfs rw,hard,intr,bg,nosuid,vers=2 0 0
marie:/d2 /nfs/marie nfs rw,hard,intr,bg,nosuid,vers=2 0 0
azide:/d2 /nfs/azide nfs rw,hard,intr,bg,nosuid,vers=2 0 0
cedric:/usr/people /nfs/cedric nfs rw,hard,intr,bg,nosuid,vers=2 0 0
Note how you can comment the file and comment out mounts.
Dow
Dow Hurst wrote:
> What you want to do is limit the machine2 on the client side not the
> server side. Only mount /dir/subdir onto the machine2 as /something
> and then you won't have the parent directory available at all.
>
> Plus, I believe the export command supports:
>
> /dir -rw=machine1:machine2,access=machine1:machine2
>
> for the syntax when having specific machine access.
> Dow
>
>
> ChangingLINKS.com wrote:
>
>> yes.
>>
>> On Thursday 13 February 2003 8:38 am, Michael D. Hirsch wrote:
>>
>>
>>> On Thursday 13 February 2003 04:42 am, ChangingLINKS.com wrote:
>>>
>>>
>>>> I have an NFS server. The exports file was like so:
>>>>
>>>> /dir user1(rw)
>>>> /dir user2(rw)
>>>>
>>>
>>> Where you wrote "user1' and "user2" you menat "machine1" and
>>> "machine2", right? I don't think nfs has and per-user permissions.
>>>
>>> --Michael
>>> _______________________________________________
>>> Ale mailing list
>>> Ale at ale.org
>>> http://www.ale.org/mailman/listinfo/ale
>>>
>>>
>>>
>>
>>
>>
>>
>
--
__________________________________________________________
Dow Hurst Office: 770-499-3428
Systems Support Specialist Fax: 770-423-6744
1000 Chastain Rd., Bldg. 12
Chemistry Department SC428 Email:dhurst at kennesaw.edu
Kennesaw State University Dow.Hurst at mindspring.com
Kennesaw, GA 30144
*********************************
*Computational Chemistry is fun!*
*********************************
_______________________________________________
Ale mailing list
Ale at ale.org
http://www.ale.org/mailman/listinfo/ale
More information about the Ale
mailing list