From owner-freebsd-stable Tue Mar 18 12:55:57 2003 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 20DEC37B404 for ; Tue, 18 Mar 2003 12:55:55 -0800 (PST) Received: from PIKES.panasas.com (gw2.panasas.com [65.194.124.178]) by mx1.FreeBSD.org (Postfix) with ESMTP id 157EB43F3F for ; Tue, 18 Mar 2003 12:55:54 -0800 (PST) (envelope-from cbehanna@panasas.com) Received: from waumbek.panasas.com ([172.17.2.36]) by PIKES.panasas.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id XA3FC6L4; Tue, 18 Mar 2003 15:55:53 -0500 From: Chris BeHanna Reply-To: cbehanna@panasas.com Organization: Panasas, LLC To: stable@freebsd.org Subject: Re: setting kern.ngroups Date: Tue, 18 Mar 2003 15:55:52 -0500 User-Agent: KMail/1.5 References: <4394.192.168.1.5.1048003806.squirrel@wuhjuhbuh.afraid.org> <1048011633.2072.1.camel@pyanfar.ece.cmu.edu> <1372.192.168.1.5.1048020389.squirrel@wuhjuhbuh.afraid.org> In-Reply-To: <1372.192.168.1.5.1048020389.squirrel@wuhjuhbuh.afraid.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200303181555.52996.cbehanna@panasas.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tuesday 18 March 2003 15:46, Brian Szymanski wrote: > > On Tue, 2003-03-18 at 12:28, Brian Szymanski wrote: > >> > Raising the maximum number of groups requires changes all over the > >> > >> place; even if you find them all and rebuild the world (yes, libc > >> depends on it as well) you'll find that any program that looks at > >> the group vector will blow up because it only has space reserved for > >> 16 groups. You don't want to go there. > >> > >> Aren't these programs broken by not using NGROUPS_MAX from > >> syslimits.h? > > > > My point is that changing syslimits.h doesn't help existing compiled > > code at all; you need to recompile everything that touches the group > > vector, which may be more code than you expect. (Arguably they should > > use a runtime method of sizing the group vector but I've seen very few > > programs that do.) > > Ahhh, no problem. Fortunately we have source for all the code we are > running on the machine... > > Which brings up another question. Does anyone know of a good way to > rebuild all ports, without dealing with dependency hell? Stupi^H^H^H^H^HBrave souls can do so via: cd /usr/ports/sysutils/portupgrade make install clean # edit /usr/local/etc/pkgtools.conf to taste portsdb -uU pkgdb -uF portupgrade -af # # wait a very long time if you have X + KDE or X + GNOME installed # otherwise, wait a merely long time That will rebuild *everything*. It gives me the shudders, though, because there are inevitably going to be broken ports. It's a good idea to save the old packages portupgrade makes for awhile, so that you can back out a broken port to the previous known working version (when that is possible). -- Chris BeHanna Software Engineer (Remove "bogus" before responding.) behanna@bogus.zbzoom.net Turning coffee into software since 1990. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message