SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
NFS can't limit group memberships, that doesn't make sense on a normal posix filesystem. A file just has a uid and a gid, NFS has no idea at all how many users are in the groups, that logic would have to live elsewhere. Can you demonstrate the behaviour you're referring to in more detail? if this something to do with the export on NFS maybe? Lots of groups listed in there??
OK, so checking around I see what you're probably referring to. It's not NFS but the RPC authentication stages. I asked you to provide more information and you didn't... just saying "you're wrong" is somewhere short of useful.
So to move forwards, do you need all these groups? 16 groups is a lot for a posix account to be part of, I'd really think that it's been poorly managed along the way to evolve into so many gorup memberships. You can apparently look to use gss authentication (kerberos) with nfsv4 to work around the default auth methods. 10 seconds on google brings up this useful blog entry: http://nfsworld.blogspot.com/2005/03...imitation.html
Last edited by acid_kewpie; 12-19-2010 at 10:57 AM.
Nfs v4 is VERY different from v2 / v3, different models and practises, it's not just a code upgrade. You should have v4 support there by default, but you'll need to read up on it, and reconfigure your clients completely too.
This thread reminded me of this one, though it won't really help you.
This thread seems to still apply (unfortunately), so it will require some extra dependencies (note that they may have changed since then...you'll have to check) and a recompile of nfs-utils. I'm not sure if enabling NFSv4 would require modifying the startup scripts or not.
It looks that NFS v.4 is not easily available in Slackware. Do you maybe know if other distros (ie. Fedora) have NFSv.4 compiled by default? BTW: I`m not sure if NFSv.4 alone solves the problem with 16 groups limit. Can anyone advise if this is only half of the solution and I have to change authentication method, too?