From owner-freebsd-hackers Tue Jan 21 17:56:16 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id RAA02376 for hackers-outgoing; Tue, 21 Jan 1997 17:56:16 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id RAA02370 for ; Tue, 21 Jan 1997 17:56:13 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id MAA11175; Wed, 22 Jan 1997 12:25:44 +1030 (CST) From: Michael Smith Message-Id: <199701220155.MAA11175@genesis.atrad.adelaide.edu.au> Subject: Re: Cannot fork In-Reply-To: from Warner Losh at "Jan 21, 97 05:26:23 pm" To: imp@village.org (Warner Losh) Date: Wed, 22 Jan 1997 12:25:43 +1030 (CST) Cc: hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Warner Losh stands accused of saying: > > Any ideas on how I might track down this problem? I'm rebuilding my > kernel now with MAX_CHILDREN set to be 256 rather than whatever the > default is. We'll see if that is the problem. Over time I keep > bumping limits and I'm fine for a while, but after a while I start to > hit the cannot fork messages again. What does 'limit maxproc' say? I usually raise it to 200 or so in my .xsession; the default of 40 or so is very tight for heavy X work. > Warner -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[