From owner-freebsd-questions  Wed Aug 12 02:21:32 1998
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id CAA26541
          for freebsd-questions-outgoing; Wed, 12 Aug 1998 02:21:32 -0700 (PDT)
          (envelope-from owner-freebsd-questions@FreeBSD.ORG)
Received: from implode.root.com (implode.root.com [198.145.90.17])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA26506
          for <questions@FreeBSD.ORG>; Wed, 12 Aug 1998 02:21:22 -0700 (PDT)
          (envelope-from root@implode.root.com)
Received: from implode.root.com (localhost [127.0.0.1])
	by implode.root.com (8.8.5/8.8.5) with ESMTP id CAA20246;
	Wed, 12 Aug 1998 02:21:13 -0700 (PDT)
Message-Id: <199808120921.CAA20246@implode.root.com>
To: Doug White <dwhite@resnet.uoregon.edu>
cc: Haavard Vaagstoel <havardjv@gudmund.vgs.no>, questions@FreeBSD.ORG
Subject: Re: proc: table is full 
In-reply-to: Your message of "Wed, 12 Aug 1998 00:08:28 PDT."
             <Pine.BSF.4.00.9808120007320.28795-100000@resnet.uoregon.edu> 
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Wed, 12 Aug 1998 02:21:13 -0700
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>> I got the following message while trying to install the port for
>> xlockmore (it actually occured during the registration of the
>> installation):
>> 
>> cannot fork
>> /kernel: proc: table is full
>> 
>> In case it can be of any help, "uname -a" shows:
>> 
>> FreeBSD gealach.myst.no 2.2.7-STABLE FreeBSD 2.2.7-STABLE #0: Sun Aug  9 
>> 16:57:47 CEST 1998     root@gealach.myst.no:/usr/src/sys/compile/GEALACH 
>> i386
>> 
>> 
>> The problem has occured several times while compiling. What do I need to
>> do to prevent it from happening again?
>
>You're hitting user limits  Run 'unlimit' (or your shell equivalent) to
>release the limits to the max for your login class.  If that doesn't help
>hack /etc/login.conf.  Don't forget to rebuild it's database!

   Actually, the panic occurs because his system is running out of processes.
This might be due to a runaway fork, or it might be due to maxusers being
set too low in his kernel config file.

-DG

David Greenman
Co-founder/Principal Architect, The FreeBSD Project

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message