From owner-freebsd-bugs@FreeBSD.ORG Thu Nov 27 02:10:12 2003 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 389EC16A4CE for ; Thu, 27 Nov 2003 02:10:12 -0800 (PST) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 881D943FCB for ; Thu, 27 Nov 2003 02:10:11 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.9/8.12.9) with ESMTP id hARAABFY088300 for ; Thu, 27 Nov 2003 02:10:11 -0800 (PST) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.9/8.12.9/Submit) id hARAAB9M088299; Thu, 27 Nov 2003 02:10:11 -0800 (PST) (envelope-from gnats) Date: Thu, 27 Nov 2003 02:10:11 -0800 (PST) Message-Id: <200311271010.hARAAB9M088299@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Bruce Evans Subject: Re: kern/58803: kern.argmax isn't changeable even at boot [PATCH] X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Bruce Evans List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Nov 2003 10:10:12 -0000 The following reply was made to PR kern/58803; it has been noted by GNATS. From: Bruce Evans To: Per Hedeland Cc: freebsd-gnats-submit@freebsd.org Subject: Re: kern/58803: kern.argmax isn't changeable even at boot [PATCH] Date: Thu, 27 Nov 2003 21:02:24 +1100 (EST) On Sun, 23 Nov 2003, Per Hedeland wrote: > Bruce Evans wrote: > > > >On Sun, 2 Nov 2003, Per Hedeland wrote: > >> ... > >> So, would the patch be acceptable if it also > >> > >> a) Fixed the usage of ARG_MAX in the source tree > >> b) Made the constant definition be equal to _POSIX_ARG_MAX > >> c) Prevented setting the tunable lower than _POSIX_ARG_MAX > >> > >> ? Removing the definition altogether would of course be just as simple > >> as b), > > > >That would be enough for me, except don't do (b) (leave ARG_MAX with its > >current value which is larger than _POSIX_ARG_MAX until most or all ports > >are fixed). Fixing all ports is too much to expect from anyone. > > OK, I finally got around to looking at this again - an "interesting" > exercise... An updated patch is enclosed. This seems to be along the right lines. I hope to commit it (with some style changes) the release freeze. (Actually, I hope someone else will do this :-). Someone pointed to a similar problem with NGROUPS_MAX and NGROUPS. It seems to be easier to fix. Bruce