Re: Bug#325465: Difference between sysconf(_SC_NGROUPS_MAX) and /proc/sys/kernel/ngroups_max
>Sylvain Beucler wrote:
>> On Wed, Aug 31, 2005 at 01:31:32PM +0900, GOTO Masanori wrote:
>> > Version: 2.3.5-3
>> >
>> > At Mon, 29 Aug 2005 20:09:29 +0200,
>> > Sylvain Beucler wrote:
>> > > As far as I understand, sysconf() should get the information at run
>> > > time. How comes that he returns 32 on a system that support 65536?
>> >
>> > At least with 2.3.5-6 in unstable, the problem should be fixed - it
>> > looks /proc/sys/kernel/ngroups_max.
>>
>> I noted that the problem didn't exist in unstable.
>>
>> Is there a way to fix this in stable?
>
>I don't think so, since it is part of the stable definition to not risk
>breakage by fixing more than the catastrophic bugs.
>
<> This is blocker and preventing us from supporting additional SCMs at
>> Savannah.gnu.org, since several users are parts of LOTS of projects,
>> and hence belong to LOTS of Unix groups :) We currently have a very
<> unusual CVS setup that works around this bug, but we cannot apply that
>> trick to other SCMs.
>Well, there's always the possibility to use a patched glibc package.
Where?? My problem is I have a CVS server, with debian sarge (stable) there are many users with more than 32 supp. groups,
I tried 2.4 2.6 kernels, also rebuild glibc, but the NGROUPS_MAX 32 limits is still in use..
Any tip should help.
Thanking in advance,
Emilio
Reply to: