Date: Thu, 27 Nov 2003 02:10:11 -0800 (PST) From: Bruce Evans <bde@zeta.org.au> To: freebsd-bugs@FreeBSD.org Subject: Re: kern/58803: kern.argmax isn't changeable even at boot [PATCH] Message-ID: <200311271010.hARAAB9M088299@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/58803; it has been noted by GNATS. From: Bruce Evans <bde@zeta.org.au> To: Per Hedeland <per@hedeland.org> 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 <bde@zeta.org.au> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200311271010.hARAAB9M088299>