From owner-freebsd-current Tue Oct 2 5:19:22 2001 Delivered-To: freebsd-current@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id 9783537B408; Tue, 2 Oct 2001 05:19:11 -0700 (PDT) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.6/8.11.2) id f92CH7f21500; Tue, 2 Oct 2001 15:17:07 +0300 (EEST) (envelope-from ru) Date: Tue, 2 Oct 2001 15:17:07 +0300 From: Ruslan Ermilov To: Robert Watson Cc: current@FreeBSD.ORG Subject: Re: Review: change NGROUPS_MAX from 16 to 64 Message-ID: <20011002151707.D18632@sunbay.com> References: <20011002115206.M74839@sunbay.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from rwatson@FreeBSD.ORG on Tue, Oct 02, 2001 at 08:12:45AM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Probably, the reason is to still have a working KINFO_PROC_SIZE even if the user modifies NGROUPS_MAX? On Tue, Oct 02, 2001 at 08:12:45AM -0400, Robert Watson wrote: > > On Tue, 2 Oct 2001, Ruslan Ermilov wrote: > > > What's the reason why KI_NGROUPS should be different from NGROUPS_MAX? > > None -- ideally, they would be the same. I was reminding him that if he > updated one, he should be sure to update the other. > > > On Mon, Oct 01, 2001 at 05:04:51PM -0400, Robert Watson wrote: > > > > > > Note this will break binary compatibility for xucred. Note also that this > > > may have fascinating effects in NFS environments. Note also that you'll > > > probably want to update KI_NGROUPS also. No idea if it will affect NIS. -- Ruslan Ermilov Oracle Developer/DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message