From owner-freebsd-questions Sun Apr 26 00:13:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA05655 for freebsd-questions-outgoing; Sun, 26 Apr 1998 00:13:05 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from xcf.berkeley.edu (scam.XCF.Berkeley.EDU [128.32.43.201]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id AAA05645 for ; Sun, 26 Apr 1998 00:12:50 -0700 (PDT) (envelope-from nordwick@xcf.berkeley.edu) Received: (qmail 6580 invoked by uid 27268); 26 Apr 1998 07:14:06 -0000 Date: 26 Apr 1998 07:14:06 -0000 Message-ID: <19980426071406.6579.qmail@xcf.berkeley.edu> From: Jason Nordwick MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: John Cavanaugh Cc: questions@FreeBSD.ORG Subject: Re: What does /kernel: proc: table is full mean? In-Reply-To: john@bang.rain.com on 4/25/1998 to questions@FreeBSD.ORG <199804251526.IAA01643@bang.rain.com> References: <199804251526.IAA01643@bang.rain.com> X-Mailer: VM 6.32 under Emacs 19.34.1 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am more questions than answers in this. John Cavanaugh, on Sat 4/25/1998, wrote the following: > > I have got a FreeBSD box running: > > FreeBSD bang.rain.com 2.1.0-RELEASE FreeBSD 2.1.0-RELEASE #0: Thu Dec 7 07:50:1 > 2 PST 1995 john@bang.rain.com:/a/src/sys/compile/BANG i386 > Whoa, stone ages; before my time :) > It had been up about 250 days with no problems when suddenly out of the blue > last night I got this: > > Apr 24 21:37:54 bang /kernel: proc: table is full > Apr 24 21:38:04 bang last message repeated 14 times > Apr 24 21:38:04 bang sendmail[28488]: NOQUEUE: SYSERR(root): SMTP-MAIL: cannot f > ork: Resource temporarily unavailable > Apr 24 21:38:04 bang /kernel: proc: table is full > I think (I am probably wrong and still new to FBSD), that this means that the kernel thinks that all process entries are taken up (I am not sure what would make it think that way, unless it really was). What was running at the time ? Does anybody know with maxusers in the kernel config affects this? > At this point, I could only get a root login and when I did I couldn't > do anything (shutdown, reboot, ps, etc.) because there were "no more > processes". I had to physically reboot the machine to get it to come > back. > Aren't a certain number of process reserved for root ? > It came back up fine but I was curious as to what would cause this problem. > What was running ? jay -- Join the FreeBSD Revolution. Support the FSF, buy GNU. http://xcf.berkeley.edu/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message