Date: Fri, 7 Dec 2001 13:32:48 -0500 From: Michael Lucas <mwlucas@FreeBSD.ORG> To: Robert Watson <rwatson@FreeBSD.ORG> Cc: arch@FreeBSD.ORG Subject: Re: Default value for maxusers Message-ID: <20011207133248.A12700@blackhelicopters.org> In-Reply-To: <Pine.NEB.3.96L.1011207131905.42713G-100000@fledge.watson.org>; from rwatson@FreeBSD.ORG on Fri, Dec 07, 2001 at 01:21:46PM -0500 References: <Pine.NEB.3.96L.1011207131905.42713G-100000@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
As a person who actually reads -questions, -stable, etc, and trolls for new FAQs: Please upsize maxusers. Please. Either GENERIC or tuning(7) should be fixed, and maxusers is too low for most of our users. 64 would be fine for most people. People running on a 386-486 will be customizing their kernels anyway. ==ml On Fri, Dec 07, 2001 at 01:21:46PM -0500, Robert Watson wrote: > > While reviewing and updating the content of tuning(7), I noticed the > following text: > > The kern.maxusers tunable defaults to an incredibly low value. For most > modern machines, you probably want to increase this value to 64, 128, or > 256. We do not recommend going above 256 unless you need a huge number > of file descriptors. Network buffers are also affected but can be > controlled with a separate kernel option. Do not increase maxusers just > to get more network mbufs. Systems older than FreeBSD 4.4 do not have > this loader tunable and require that the kernel config(8) option maxusers > be set instead. > > The first two sentences suggest that either we need to do one of the > following: > > (1) Update the default maxusers value in GENERIC to something larger > (perhaps 64), and remove the text from tuning(7), or... > > (2) Remove this text from tuning(7). > > It seems rediculous to have a default that is known to be inadequate (or > worse, "incredibly low"). I have to admit that the first thing I do with > any box is either recompile the kernel to have higher maxusers, or use > kern.maxusers in /boot/loader.conf to update it to at least 64. If we > believe the observations above are correct, the choice seems simple: > update GENERIC, and I'd be happy to commit that to at least -CURRENT, and > possibly -STABLE. If they're not, we should moderate the description > above a bit :-). > > Robert N M Watson FreeBSD Core Team, TrustedBSD Project > robert@fledge.watson.org NAI Labs, Safeport Network Services > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-arch" in the body of the message -- Michael Lucas mwlucas@FreeBSD.org, mwlucas@blackhelicopters.org http://www.blackhelicopters.org/~mwlucas/ Big Scary Daemons: http://www.oreillynet.com/pub/q/Big_Scary_Daemons To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20011207133248.A12700>