From owner-freebsd-current Tue Jun 11 00:26:08 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA10609 for current-outgoing; Tue, 11 Jun 1996 00:26:08 -0700 (PDT) Received: from soda.CSUA.Berkeley.EDU (soda.CSUA.Berkeley.EDU [128.32.43.52]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id AAA10604 for ; Tue, 11 Jun 1996 00:26:06 -0700 (PDT) Received: (from richardc@localhost) by soda.CSUA.Berkeley.EDU (8.6.12/8.6.12) id AAA10451; Tue, 11 Jun 1996 00:26:10 -0700 Date: Tue, 11 Jun 1996 00:26:09 -0700 (PDT) From: Veggy Vinny To: dwhite@resnet.uoregon.edu cc: current@FreeBSD.org Subject: Re: console messages In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 11 Jun 1996, Doug White wrote: > On Sat, 8 Jun 1996, Veggy Vinny wrote: > > > I'm running the June 3rd, 1996 FreeBSD-current and it seems on a > > machine with a Intel Neptune based Dual P5-100 system with 128 megs of > > RAM and 300 megs of disk swap, we keep getting the following message and > > then the machine reboots or just hangs there, any ideas what can be > > causing this? > > > > /kernel: proc: table is full > > Increase MAXUSERS in the kernel config. It's already at 128... > > swap_pager: out of swap space > > Add some swap to the system. There is already 300MB of swap and it does that when it's at 20%.. > Sounds like you have a heavily used machine. I would guess to crank > maxusers to 200 (? - check me !!) and have 250-300MB of swap. (2*memory) > > No doubt others will have different opinions. Well, that is already there... Vince