From owner-freebsd-ports Wed Jan 30 10:27:44 2002 Delivered-To: freebsd-ports@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id 490B237B405; Wed, 30 Jan 2002 10:27:41 -0800 (PST) Received: (from dan@localhost) by dan.emsphone.com (8.11.6/8.11.6) id g0UIRcS31767; Wed, 30 Jan 2002 12:27:38 -0600 (CST) (envelope-from dan) Date: Wed, 30 Jan 2002 12:27:38 -0600 From: Dan Nelson To: Emiel Kollof Cc: current@FreeBSD.ORG, ports@FreeBSD.ORG Subject: Re: many copies of make running while building a port... Message-ID: <20020130182737.GS92289@dan.emsphone.com> References: <86263CF3-1547-11D6-A3B8-000A277C7FDE@hackerheaven.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <86263CF3-1547-11D6-A3B8-000A277C7FDE@hackerheaven.org> User-Agent: Mutt/1.3.25i X-OS: FreeBSD 5.0-CURRENT X-message-flag: Outlook Error Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org In the last episode (Jan 30), Emiel Kollof said: > Just a question: It seems while building a port, the ports system > somehow spawns hundreds and hundreds of copies of make (even so much > that they start hitting system limits). What's causing it, and how do > I make it stop doing that. > > Number of procs in top(1) shoot up into the ranges of 600+ procs (and > usually defunct). Load average sometimes jumps up into the 100+ (I > kid you not). I doubt that that is desired operation. I only started > seeing this behavior when I switched over to CURRENT, but this mail > is cc'd to ports@ too, just in case. It makes using portupgrade(1) as > tense as a good thriller flick (will my system survive? The > suspense!) I've had that happen when I put typos in /etc/make.conf (i.e. syntax errors or HAVE_/WANT_ variables that don't belong there). -- Dan Nelson dnelson@allantgroup.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message