From owner-freebsd-questions Wed Jan 23 18:26:39 2002 Delivered-To: freebsd-questions@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.122.47]) by hub.freebsd.org (Postfix) with ESMTP id E1A4F37B405 for ; Wed, 23 Jan 2002 18:26:36 -0800 (PST) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.11.3/8.10.1) with ESMTP id g0O2R3I66471; Wed, 23 Jan 2002 18:27:03 -0800 (PST) Date: Wed, 23 Jan 2002 18:27:03 -0800 (PST) From: Doug White To: Mario Doria Cc: questions@freebsd.org Subject: Re[2]: Strange lock-ups during backup over nfs after adding 1024M RAM In-Reply-To: <001201c1a47d$faf08ae0$0a00a8c0@Deathstar> Message-ID: <20020123182636.V56623-100000@resnet.uoregon.edu> X-All-Your-Base: are belong to us MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, 23 Jan 2002, Mario Doria wrote: > >Drop this to 128, definitely. If you're doing a lot of network, monitor > >your mbuf usage and override that if necessary. > > I had the same problem, but I removed the extra RAM from the machine. > > What's better, to hardcode maxusers 128 in the kernel or let it be maxusers > 0 and let the system auto-size the parameter? I would suggest fixing it, although you're welcome to test the autosizing. I think it caps out at 512MB anyway. > Also, is this autosized on every boot or whenever a kernel is built? It's done on boot. Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message