From: Stephan Henningsen <sth@amplex.dk>
To: nfs@lists.sourceforge.net
Subject: Re: Trouble accessing NFS mountpoint as user
Date: Thu, 04 Jan 2007 11:22:06 +0100 [thread overview]
Message-ID: <459CD54E.9050107@amplex.dk> (raw)
In-Reply-To: <1167901767.6046.17.camel@lade.trondhjem.org>
Trond Myklebust wrote:
> NFS will only support a maximum of 16 supplemental groups. That is a
> protocol limitation, not a Linux implementation issue.
I just did "chgrp dialout /var/files" on the server, changing to one of the
first 16 supplemental groups, and now it works. Thank you very much for
solving this mystery!
> See for instance
> http://nfsworld.blogspot.com/2005/03/whats-deal-on-16-group-id-limitation.html
> if you want a more complete explanation of why this is the case.
This suggests moving from NFS3 to NFS4. Is that an easy task? Mount as
"nfs4" instead of "nfs" and compile the kernel nfs server to support nfs4?
--
Stephan Henningsen
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2007-01-04 10:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-04 8:23 Trouble accessing NFS mountpoint as user Stephan Henningsen
2007-01-04 9:09 ` Trond Myklebust
2007-01-04 10:22 ` Stephan Henningsen [this message]
2007-01-04 21:00 ` Frank van Maarseveen
2007-01-05 6:56 ` Stephan Henningsen
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=459CD54E.9050107@amplex.dk \
--to=sth@amplex.dk \
--cc=nfs@lists.sourceforge.net \
/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.