From owner-freebsd-hackers Mon Mar 15 18:16:48 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id 9CFE714DA7 for ; Mon, 15 Mar 1999 18:16:45 -0800 (PST) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (monica.cs.rpi.edu [128.213.7.2]) by cs.rpi.edu (8.9.1/8.9.1) with ESMTP id VAA24377 for ; Mon, 15 Mar 1999 21:16:27 -0500 (EST) Message-Id: <199903160216.VAA24377@cs.rpi.edu> To: freebsd-hackers@freebsd.org Subject: evil maxusers Date: Mon, 15 Mar 1999 21:16:26 -0500 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What is evil abuot large maxusers? We have a crashing server (Pentium II-400) with maxusers set to 320. In a previous email to -hackers that I have since lost :I it was mentioned that you could lower maxusers, and the, by hand, up the MBUFs and NPROCs in the config file. However I have grepped the entire kernel source tree, and I can see that MAXUSERS is only used to set MBUFs and NPROCS (and other things derive from there, suich as MAXFILES). Why therefore will MAXUSERS=320 crash my system, while setting MAXUSERS to 64, and adjusting MBUFs and NPROCS by hand will not? -- David Cross To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message