From: Daniel Brunner <daniel.brunner@dunidester.com>
Subject: Re: nfs permissions / access problem
Date: Tue, 13 Aug 2002 10:20:49 -0500
Sender: nfs-admin@lists.sourceforge.net
Message-ID: <3FB52D0C-AED0-11D6-92E7-00306589E6DA@dunidester.com>
References: <20020813143423.QHGF221.sccrmhc02.attbi.com@there>
Mime-Version: 1.0 (Apple Message framework v482)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Cc: nfs@lists.sourceforge.net
To: nl@lippman.org
In-Reply-To: <20020813143423.QHGF221.sccrmhc02.attbi.com@there>
Errors-To: nfs-admin@lists.sourceforge.net

Hello!!

What's you /etc/exports look like!?!?

/shared	195.168.100.0/255.255.255.0(rw)
....


Use whatever your ip number is...


Dan


On Tuesday, August 13, 2002, at 09:38 AM, nl@lippman.org wrote:

> I am hoping someone can provide some advice. The situation is that I 
> want to
> have available on my nfs server a share that is accessible to a group of
> people connecting from their workstations, but am having trouble doing 
> so.
>
> Following what I would have done for a local directory, I created the
> directory: /shared and set its ownship to root, with group=sharedgroup, 
> and
> then gave group permissions of rwx. I made sure each user who needs to 
> use
> the shared directory is in the sharedgroup on the server, and for good
> measure also did so on each workstation (and yes, the gid's are the 
> same on
> each machine). Unfortunately, the directory remains inaccessible via 
> nfs with
> this scheme.
>
> I suspect the problem here is that nfs receives from the client the uid 
> and
> gid that the client process is currently executing under, but does not
> received the extended group list, and also does not look up that user's
> extended group list on the server but rather just does permission 
> checking
> with the single active uid and gid it received from the client, and so 
> cannot
> access via extended group information.
>
> That doesn't strike me as the best way for nfs to operate, although I 
> am am
> sure there was sound design decision involved (maybe overhead of 
> looking up
> the groups on each access, which the os does not have locally as that 
> info is
> already in the process's state information, placed there at login).
>
> In any case, it means that I cannot easily export a shared directory in 
> this
> fashion.
>
> So my question is: How do I make an exported folder accessible to a 
> group of
> users?
>
> Thanks.
> nl
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by: Dice - The leading online job board
> for high-tech professionals. Search and apply for tech jobs today!
> http://seeker.dice.com/seeker.epl?rel_code=31
> _______________________________________________
> NFS maillist  -  NFS@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nfs


-------------------------------------------------------
This sf.net email is sponsored by: Dice - The leading online job board
for high-tech professionals. Search and apply for tech jobs today!
http://seeker.dice.com/seeker.epl?rel_code=31
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs