linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: steve <steve@steve-ss.com>
Cc: Jeff Layton <jlayton@poochiereds.net>, linux-nfs@vger.kernel.org
Subject: Re: POSIX acls over nfs4
Date: Wed, 29 Feb 2012 07:44:01 -0500	[thread overview]
Message-ID: <20120229124401.GA9160@fieldses.org> (raw)
In-Reply-To: <4F4D61B6.5090304@steve-ss.com>

On Wed, Feb 29, 2012 at 12:22:30AM +0100, steve wrote:
> We are authenticating against Samba4, so our domain user accounts
> are under Kerberos.

Kerberos works fine with v3.

--b.

> We could wait for the s4 cifs fileserver and
> winbind to be ready but would rather stick with nfs for our Linux
> clients. Simple reason being that it beats cifs on speed, especially
> when the lan is busy.
> 
> Is there an option to turn off the nfs4 acl's? I see that there is a
> -o noacl mount option but it seems to have no effect for us.
> 
> Guys, basically we don't know where to turn next. We have this issue
> open here, and on the samba and openSUSE lists. Is there anyway we
> can get together to thrash this out?
> 
> Thanks so much for replying.
> Cheers,
> Steve pp the Spanish team at lcb
> 
> 
> >
> >--b.
> >
> >>Mounting with -o nofacl in the hope that the POSIX acl set on the
> >>unmounted directory would take effect, seems to have no effect.
> >>
> >>What I'm doing at the moment is scanning the unmounted directory
> >>every few seconds using 'find' and changing the files to g+rw:-(
> >>
> >>Thanks,
> >>Steve
> >>--
> >>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
> 

  reply	other threads:[~2012-02-29 12:44 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-18 20:08 POSIX acls over nfs4 steve
2012-02-19 17:15 ` steve
2012-02-23  7:15   ` steve
2012-02-23  8:33     ` tao.peng
2012-02-23 12:50       ` steve
2012-02-23 11:39     ` Jeff Layton
2012-02-23 11:53       ` steve
2012-02-23 14:40         ` J. Bruce Fields
2012-02-23 15:33           ` steve
2012-02-23 15:42             ` J. Bruce Fields
2012-02-23 16:08               ` steve
2012-02-25  8:19                 ` steve
2012-02-28 20:05                   ` J. Bruce Fields
2012-02-28 23:22                     ` steve
2012-02-29 12:44                       ` J. Bruce Fields [this message]
2012-02-29 14:04                         ` steve
2012-02-29 14:09                           ` J. Bruce Fields
2012-02-29 14:26                             ` steve
2012-02-29 14:32                               ` J. Bruce Fields
2012-02-29 14:40                                 ` steve
2012-03-01 20:56                                   ` J. Bruce Fields
2012-03-01 22:11                                     ` steve
2012-03-02 18:03                                       ` J. Bruce Fields
2012-02-28 20:00                 ` J. Bruce Fields

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=20120229124401.GA9160@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=jlayton@poochiereds.net \
    --cc=linux-nfs@vger.kernel.org \
    --cc=steve@steve-ss.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).