nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

TS on Solaris and groups

Valentine

Have anybody tried increasing the number of users per group in Solaris?

Default is 16, but it could be raised with

modifying /etc/system
set ngroups_max = 32

Sun documentation that it might cause problems with NFS. Since TS is using local NFS, I am a little bit concerned with that.

Find more posts tagged with

Comments

Migrateduser

We were told that we could bump it up to 32, but 32 is not nearly enough either. There's no point. 16 or 32...that's still dozens away from where we need it to be. Give me a call when they up it to 1000.

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com

Drew_The_Goat

Hi Smitty,

We too use up a lot of Solaris groups for user permissions, and we are creeping closer to the 32 group limit. For example, ever new branch must have a unique group permission, and there are various sub groups for each branch.

How are you managing the group limit in Solaris?? We have not changed the /etc/system file either, yet Teamsite users are working with with 16+ groups.

Thanks,
Drew

Migrateduser

Check out the thread titled map_secondary_to_primary_gid, most specifically this post:

http://devnet.interwoven.com/forums/cgi-bin/showthreaded.pl?Cat=&Board=PRODUCTS_TEAMSITE&Number=27904&page=0&view=expanded&sb=5&o=0&vc=1#Post27904

for a detailed description of how we are doing things. We use the map_secondary_to_primary_gid flag in TeamSite to attempt to get around the Solaris group limitation, but it isn't working completely. So far I have found no other workaround or solution. It's very frustrating.

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com

Adam Stoller

Have anybody tried increasing the number of users per group in Solaris?

FYI: It's groups per user not users per group which is the issue here, and the limitation is, I believe, in NFS, not Solaris.

The limitation on how many users may belong to a group is a different issue, and I believe may be a Solaris limitation.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Valentine

I do not think there is a reasonable limit on the number of users in the group. Solaris can handle 32 groups per user, by default it is 16.

However the NFS implementation can deal only with 16, and since TS uses NFS, it is not a solution 8(

Ninerfan

We ran into this problem as well. We had some users who needed to belong to more than 16 groups which is the NFS limit. We put this line in the iw.cfg and it worked great.

map_secondary_to_primary_gid=yes

Only issue we have seen is that you can no longer trust GID you see on Solaris cmd line because TeamSite is remapping them constantly. You can however look at the "File Properties" in TeamSite GUI to see the real permissions and ownership settings.

We are running TS 5.5.2 SP2 on Solaris 2.8.

Another option might be to use Native LDAP support for /etc/passwd and /etc/group. Have /etc/nsswitch.conf file point to LDAP instead of files. Then I think you could have users in as many groups as you want with out the remapping entry in iw.cfg. I have not done that before though so it's just a thought.

Log1.PNG

Log2.PNG