From: MJ Jenkins <mack.jenkins@eas.gatech.edu>
To: Emmanuel Florac <eflorac@intellique.com>
Cc: <linux-nfs@vger.kernel.org>
Subject: Re: NFS Share To OS X
Date: Thu, 25 Sep 2014 13:52:33 -0400 [thread overview]
Message-ID: <54245661.8010107@eas.gatech.edu> (raw)
In-Reply-To: <20140925183034.432731eb@harpe.intellique.com>
This is the /etc/exports file. 129.169 is the Mac I'm exporting to.
129.183 is the other RHEL machine.
##### Mount point for Britney Schmidt's Mac Pro #####
/nfs/bsmac
192.168.129.169(rw,all_squash,no_subtree_check,insecure,anonuid=0)
192.168.129.183(rw,no_root_squash,no_subtree_chck)
This is /etc/fstab from the Mac.
#storage:/nfs/bsmac /data1 nfs
resvport,nolocks,locallocks,intr,soft,wsize=32768,rsize=3276
storage:/nfs/bsmac /data1 nfs
vers=3,noowners,nolocks,nolockd,nolock,nonlm,automounted,nosuid,hard,bg,noresvport,intr,rw,tcp,nfc
That 1st line in /etc/fstab is another way I was mounting the share
trying to solve this one.
Thanks for any assistance that can be provided.
Mack
On 09/25/2014 12:30 PM, Emmanuel Florac wrote:
> Le Thu, 25 Sep 2014 09:15:24 -0400
> MJ Jenkins <mack.jenkins@eas.gatech.edu> écrivait:
>
>> The problem comes in when the user on the Mac writes files to the NFS
>> share. On the RHEL side the files are owned by user root and group
>> nfsnobody. Has anyone else run into this issue? I'm not sure if the
>> issue is how I am exporting the share to the Mac, or how I have the
>> share mounted on the Mac.
> Without the content of your /etc/exports, it's impossible to know
> what's happening. Mac behave like regular NFS clients. Maybe you have
> "all_squash,anonuid=0,anongid=5" in your export parameter, maybe it's
> something else entirely.
>
next prev parent reply other threads:[~2014-09-25 17:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-25 13:15 NFS Share To OS X MJ Jenkins
2014-09-25 16:30 ` Emmanuel Florac
2014-09-25 17:14 ` Mauricio Tavares
2014-09-25 17:52 ` MJ Jenkins [this message]
2014-09-26 7:52 ` Emmanuel Florac
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54245661.8010107@eas.gatech.edu \
--to=mack.jenkins@eas.gatech.edu \
--cc=eflorac@intellique.com \
--cc=linux-nfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.