From owner-freebsd-stable Thu Jul 4 9:35:22 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 420B337B400 for ; Thu, 4 Jul 2002 09:35:20 -0700 (PDT) Received: from samwise.jobeus.net (samwise.jobeus.net [209.91.102.74]) by mx1.FreeBSD.org (Postfix) with ESMTP id 953DA43E31 for ; Thu, 4 Jul 2002 09:35:19 -0700 (PDT) (envelope-from freebsd@jobeus.net) Received: (from root@localhost) by samwise.jobeus.net (8.12.5/8.12.3) id g64GZCcP089306 for stable@freebsd.org; Thu, 4 Jul 2002 10:35:12 -0600 (MDT) (envelope-from freebsd@jobeus.net) Received: from localhost (freebsd@localhost [127.0.0.1]) by samwise.jobeus.net (8.12.5/8.12.3av) with ESMTP id g64GZASe089298 for ; Thu, 4 Jul 2002 10:35:10 -0600 (MDT) (envelope-from freebsd@jobeus.net) Date: Thu, 4 Jul 2002 10:35:10 -0600 (MDT) From: Scott Carmichael To: stable@freebsd.org Subject: Interesting 'rogue' problem. Message-ID: <20020704103146.S89292-100000@samwise.jobeus.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS perl-11 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In the game Rogue, if a user quits (shift-Q) chooses 'yes' to quit, and while being told how much gold they're quitting with suspends the program (ctrl-z) and then exits the system (ignoring the 'there are suspended jobs' warning), rogue will then proceed to eat up all the CPU resources on the CPU as shown in this output of 'top': PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND 89270 jobe 64 0 1320K 968K RUN 1:11 97.92% 96.39% rogue 2923 jobe 66 19 16552K 15980K RUN 786:01 2.25% 2.25% setiathome It's even taking the processing time away from setiathome, it's so strong! :) Any input on why this might be happening? Thanks, Scott Carmichael http://jobeus.net/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message