From owner-freebsd-current  Tue Jun 11 00:29:30 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id AAA10724
          for current-outgoing; Tue, 11 Jun 1996 00:29:30 -0700 (PDT)
Received: from riley-net170-164.uoregon.edu (riley-net170-164.uoregon.edu [128.223.170.164])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id AAA10719
          for <current@FreeBSD.org>; Tue, 11 Jun 1996 00:29:28 -0700 (PDT)
Received: (from dwhite@localhost) by riley-net170-164.uoregon.edu (8.6.12/8.6.12) id AAA05164; Tue, 11 Jun 1996 00:31:12 -0700
Date: Tue, 11 Jun 1996 00:31:12 -0700 (PDT)
From: Doug White <dwhite@riley-net170-164.uoregon.edu>
Reply-To: dwhite@resnet.uoregon.edu
To: Veggy Vinny <richardc@CSUA.Berkeley.EDU>
cc: current@FreeBSD.org
Subject: Re: console messages
In-Reply-To: <Pine.PTX.3.91.960611002516.22147a-100000@soda.CSUA.Berkeley.EDU>
Message-ID: <Pine.BSF.3.91.960611002844.5035O-100000@riley-net170-164.uoregon.edu>
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, Veggy Vinny wrote:

Here I go answering questions without reading the question first :-)

> > > 	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...

Maybe you have a runaway process then.  

I think I'll let the pros take it from here... this is not something I'm 
very familiar with.  

Doug White                              | University of Oregon  
Internet:  dwhite@resnet.uoregon.edu    | Residence Networking Assistant
http://gladstone.uoregon.edu/~dwhite    | Computer Science Major