Re: NFS client , automount and protection problem
- From: Kevin McMurtrie <mcmurtri@xxxxxxxxxxxxxx>
- Date: Mon, 07 Jan 2008 23:42:51 -0800
NFS isn't meant for general file sharing. It's mean to be the disk in a
cluster of managed machines. In many cases you'll have to match up UIDs
between your client and server. It's weak client-side protection but
it's good enough for environments where all hardware is physically
secure.
Since you're having problems with non-root automount, the first place to
look is at the local mount directory. I'm guessing that only root can
read the automount file so it's an opaque directory for everybody else.
You might need to chmod/chown/chgrp the directory. Once that's fixed
you can move on to fixing mismatched UIDs :)
In article <478203ed$0$15791$c3e8da3@xxxxxxxxxxxxxxxxx>,
JF Mezei <jfmezei.spamnot@xxxxxxxxxxxxx> wrote:
I have a problem with Tiger 10.4.11 , with NFS and automount.
{
"name" = ( "mounts" );
CHILDREN = (
{
"name" = ( "10.0.0.11:/disk2/users/jfmezei" );
"dir" = ( "/disk2" );
"opts" = ( "resvport" );
"type" = ( "nfs" );
}
)
}
This creates the "disk2" alias in the root.
The original is listed as /automount/static/disk2
The owner is listed as "system" read and write. (get info from finder).
Double clicking on the icon from the finder yields an "the alias disk2
could not be opened because the original count not be found" alert.
from the command line:
ls /disk2
gives: /disk2
BUT:
sudo ls /disk2
WORKS PERFECTLY (aka lists the files on the remote server).
Note that if dismount it manually (umount /private/var/automount/disk2)
And I then:
ls /disk2
I still get the /disk2 right away.
But when I do: sudo ls /disk2
it pauses. On the server, I get console message indication that uid=0
gid=0 has mounted the file system and then I get the file listing.
So when the normal user tries to access the alias, the Mac doesn't even
bother asking the remote server to mount it. But when it is root that
wants to access it, then the automount will process the request and
mount it. Same for normal access once it has been mounted.
Are there any hints on how to make automount create a mount point that
can bve access by the regular user on the Mac ? From what I had read,
this is supposed to happen by default.
Also, I have seen conflicting documentation for the netinfo setup: some
say use "vfstype = nfs" and others say "type = nfs". And in the
"options" field, what exactly can be entered ?
Would those be the arguments you would give to a mount_nfs line ?
aka: -P -T -o nfsv3 rdirplus rsize=32764
Or are those only the "-o" options that can be entered ?
Also, some of the pages I have neen on the net mention the "net" option,
but it is not in the mount_nfs man pages.
Any help trying to point me in the right direction or onto the right
documentation for Tiger would be appreciated.
--
I don't read Google's spam. Reply with another service.
.
- Follow-Ups:
- Re: NFS client , automount and protection problem
- From: JF Mezei
- Re: NFS client , automount and protection problem
- References:
- NFS client , automount and protection problem
- From: JF Mezei
- NFS client , automount and protection problem
- Prev by Date: Re: New MacBook
- Next by Date: Re: Giving Up on Leopard
- Previous by thread: NFS client , automount and protection problem
- Next by thread: Re: NFS client , automount and protection problem
- Index(es):
Relevant Pages
|
|