From owner-freebsd-questions Tue Mar 18 2:10: 2 2003 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8EA6F37B401 for ; Tue, 18 Mar 2003 02:10:00 -0800 (PST) Received: from vega.blacktrap.net (vega.blacktrap.net [194.9.222.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6FF8443F75 for ; Tue, 18 Mar 2003 02:09:59 -0800 (PST) (envelope-from oli@vega.blacktrap.net) Received: from vega.blacktrap.net (localhost [127.0.0.1]) by vega.blacktrap.net (8.12.6/8.12.6) with ESMTP id h2IAAXfc051110; Tue, 18 Mar 2003 11:10:33 +0100 (CET) (envelope-from oli@vega.blacktrap.net) Received: (from oli@localhost) by vega.blacktrap.net (8.12.6/8.12.6/Submit) id h2IAAWDn051109; Tue, 18 Mar 2003 11:10:32 +0100 (CET) Date: Tue, 18 Mar 2003 11:10:32 +0100 From: Olivier Dony To: Jan Blomqvist Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Resource temporarily unavailable Message-ID: <20030318101032.GA50668@vega.blacktrap.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i X-Spam-Status: No, hits=-32.5 required=5.0 tests=EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES, REPLY_WITH_QUOTES,USER_AGENT_MUTT version=2.50 X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp) 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 Tue, Mar 18, 2003 at 09:03:32AM +0100, Jan Blomqvist wrote: > Hi! > I have 800mhz 500mb node with freebsd 4.1, I often get this "Resource > temporarily unavailable" > I have problem to find out what kind of Resource its problem with, when I do > top command everything looks ok lots of memory free and like 80% idle, and > we have done some changes in the kernel "options MAXMEM=(512*1024) > options SHMMNI=64"and also increased maxusers to 128.This is a > example of error message: Hi, Just a couple of wild guesses : - I suppose you have no particular maxprocess limit or whatever for your login class in /etc/login.conf? You can always have a look at login.conf(5) - What does 'ps auxww' look like when this happens? Anything surprising there? 'top' only shows the first so much heavier processes, so you might not see everything. - On my box here I just ran a little test and with all limits set to 'unlimited' in login.conf I can trigger this error with a recursive shell script calling itself. It happens when about 475 processes have been spawned, and then they all die eventually and everything returns to normal. Hope this helps a bit, but people on the list have probably more information and also more relevant about this matter... good luck :-) Olivier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message