Mike:
Damn 16 group limit! It is a pain in the rear, huh? =)
We haven't tried to defy that, but here's one way to get around the 1024 characters limit - just put multiple entries in the group file with the same group name and GID, but different users. Like so:
project1:*:100:usera,userb,... project1:*:100:userc,userd,...
The caveat to this is that you CANNOT use it with NIS. If you did it would only match the first line and none of the subsequent ones. We use NIS for everything except the group file for this reason. Our group files are coppied (via cron) by each client to keep them up to date.
Good luck!
-- Jeff
-- ---------------------------------------------------------------------------- Jeff Krueger E-Mail: jeff@qualcomm.com NetApp File Server Lead Phone: 858-651-6709 IT Engineering and Support Fax: 858-651-6627 QUALCOMM, Incorporated Web: www.qualcomm.com
From mcbride2@us.ibm.com on Fri, 15 Oct 1999 17:03:34 MDT:
I am having an issue regarding the number of groups and, the numbers of users per group at our site. We have 3 toasters running 5.2.1P2 being administered by a solaris 2.5.1 serve r. We have about 75 unix style qtrees for both NFS and CIFS protocols.
I have a requirement that several users need to be in more than 16 groups. I believe modifying the Solaris kernel will not only slow down the access, but may present problems on the filer.
Also, I require to have more than 1024 characters needed per group entry. I have tried creating sub-groups and a master group within the group file(see below) - I cannot get this to work. Maybe I need to upgrade my Solaris NIS server? example: project1:*:100:usera,userb... project2:*:101:usery,userz mstproject:*:102:project1,project2
I would think someone has encountered this problem before. I would appreciate any feedback regarding these issues.
Mike McBride IBM Global Services Unix and NT Server Support mcbride2@us.ibm.com (760) 634-6239