Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 07 Feb 2007 08:00:07 -0600
From:      Eric Anderson <anderson@freebsd.org>
To:        Kostik Belousov <kostikbel@gmail.com>
Cc:        freebsd-hackers@freebsd.org
Subject:   Re: /etc/group limits (REAL limits)
Message-ID:  <45C9DB67.50602@freebsd.org>
In-Reply-To: <20070207134421.GF3304@deviant.kiev.zoral.com.ua>
References:  <45C95C04.6060402@centtech.com> <20070207120948.N31858@mp2.macomnet.net> <20070207134421.GF3304@deviant.kiev.zoral.com.ua>

next in thread | previous in thread | raw e-mail | index | archive | help
On 02/07/07 07:44, Kostik Belousov wrote:
> On Wed, Feb 07, 2007 at 12:17:51PM +0300, Maxim Konovalov wrote:
>> On Tue, 6 Feb 2007, 22:56-0600, Eric Anderson wrote:
>>
>>> On one of my boxes where I have a decent amount of (less than 50)
>>> users in a few groups, I finally hit the limit.  Not 1024 bytes
>>> though (that I know of). When that happens though, it is sooner than
>>> expected, and tools (like 'id') seg fault (and core dump).
>>>
>>> I have a sample group, and it appears to be hitting the byte limit.
>>> If I add a single additional character to the group, it will break
>>> things.
>>>     It appears to be a combination of multiple groups.
>>>
>>> Can someone with some experience in this area comment?  I can send
>>> the group file itself if needed.
>>>
>>> This box is 6.2-PRERELEASE from about mid-September.  I have also
>>> seen some issues on amd64, which I went through some debugging with
>>> Konstantin Belousov back in November (cc'ed).
>> Make sure you have rev. 1.32.8.3 of lib/libc/gen/getgrent.c.
> 
> It was very strange thing with buggy code generated by compiler. I tracked it
> down to exact assembler instruction missed in Mr. Anderson' instance of
> libc.so. After that, conversation stopped.


Sorry about that Kostik, the last message was for me to try a newer 
libc.so.6.  If I recall, I tried that too.  I'm not sure what else you 
wanted me to try.  If you have more ideas, I'm all ears.


Eric




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?45C9DB67.50602>