From owner-freebsd-questions@FreeBSD.ORG Wed Jan 7 07:19:55 2004 Return-Path: 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 1BBF516A4CE for ; Wed, 7 Jan 2004 07:19:55 -0800 (PST) Received: from server.simon1.net (user23.net263.oh.sprint-hsd.net [208.17.71.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9604643D39 for ; Wed, 7 Jan 2004 07:19:52 -0800 (PST) (envelope-from simon1@server.simon1.net) Received: from server.simon1.net (localhost [127.0.0.1]) by server.simon1.net (8.12.10/8.12.10) with ESMTP id i07FJp3D080827 for ; Wed, 7 Jan 2004 10:19:51 -0500 (EST) Received: from localhost (simon1@localhost)i07FJpYd080824 for ; Wed, 7 Jan 2004 10:19:51 -0500 (EST) Date: Wed, 7 Jan 2004 10:19:51 -0500 (EST) From: Simon1 To: questions@freebsd.org In-Reply-To: <44hdz7rdwk.fsf@be-well.ilk.org> Message-ID: References: <20040106075951.4910.qmail@www-01.iinet.net.au> <44hdz7rdwk.fsf@be-well.ilk.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: Run away CPU FreeBSD 4.9 Release #0 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Jan 2004 15:19:55 -0000 [snip] > > Some processes run away with the CPU. Screen is one of the worst offenders > > along with python.. > > The CPU starts out at about 15% and slowly ramps up to 100%. > > As the % ramps up, the priority increases up to about 60 > > If more than one screen is launched, then the will share the CPU but the > > priority still sits about 60. [..] > What's the actual problem? Are important programs failing to get cycles? I don't know the reason for the issue, but I too have had many problems with screen. (4.8 or 4.9 box?) It works, it just uses up all the CPU available. (Starting at 0.x percent going up to 100 percent) The fix was to build the screen port, and the problem(s) went away. I don't remember specifically on which releases this issue occurs, I do know that it's been more than just a single one. I've had the same issue on several different systems as well. Just build screen from ports and the issue will go away. I haven't (directly) used python before, but it's always been built from ports as a dependency of another port. That might have something to do with it. -Wolfe