From: Bryan Schumaker <bjschuma@netapp.com>
To: "Milovan Krivokapić" <milovan.krivokapic@gmail.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: Fwd: [Question] NFS and default file / folder permission
Date: Mon, 19 Nov 2012 12:22:09 -0500 [thread overview]
Message-ID: <50AA6AC1.2080201@netapp.com> (raw)
In-Reply-To: <CAGXUOGLFKKFOjPXHVhr6j7T_4VNKeai4Bmosu44Lsdbs=XJOdQ@mail.gmail.com>
On 11/19/2012 12:06 PM, Milovan Krivokapić wrote:
> Hi, a quick question:
> I have a problem regarding file permissions on NFS. Umask works for
> new files well, but if I get a file via Skype with permission like 600
> and then I put that file on NFS, it keeps permission 600 thus others
> from a group cant use it at all (I am sharing files via common group).
>
> So the question is how to enforce some default file / folder
> permission on NFS? So in this example, I put file on NFS as client
> with 600 and it turns into 660 or similar (kind like a mask).
I don't think you can... but the current behavior seems like the right thing to do, since changing permissions on files could create security problems.
The best workaround I can come up with is creating a cron job to change permissions on everything in the directory (or if you're creative enough, just the new files). Good luck!
- Bryan
>
> Is it even possible or you have any suggestions?
> Debian 6 is a NFS server, clients are Kubuntu 12.04.1 stations that
> mounted NFS exported folder.
>
> Thank you very much in advance.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2012-11-19 17:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAGXUOGKWDB11zoqZ9zofBgJhJ3Jw0mhZh9QUF8up-1LGCVQ2zw@mail.gmail.com>
[not found] ` <CAGXUOG+Px7tBTYH_9e93dOdxUweoE64aLLmRFa4BmyejC9Riug@mail.gmail.com>
2012-11-19 17:06 ` Fwd: [Question] NFS and default file / folder permission Milovan Krivokapić
2012-11-19 17:22 ` Bryan Schumaker [this message]
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=50AA6AC1.2080201@netapp.com \
--to=bjschuma@netapp.com \
--cc=linux-nfs@vger.kernel.org \
--cc=milovan.krivokapic@gmail.com \
/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.