From owner-freebsd-questions Sat Jun 9 15:33:45 2001 Delivered-To: freebsd-questions@freebsd.org Received: from mail.westol.com (mail.westol.com [63.93.137.11]) by hub.freebsd.org (Postfix) with SMTP id 1C85F37B401 for ; Sat, 9 Jun 2001 15:33:43 -0700 (PDT) (envelope-from wmoran@iowna.com) Received: (qmail 2438 invoked from network); 9 Jun 2001 22:35:13 -0000 Received: from ts01-033.helicon.net (HELO y0k8x9) (63.93.155.173) by mail.westol.com with SMTP; 9 Jun 2001 22:35:13 -0000 Message-ID: <000201c0f14d$c089b540$ad9b5d3f@y0k8x9> From: "Bill Moran" To: "Walter Hop" Cc: "FreeBSD Questions" References: <200106091245.AA1833238794@stmail.pace.edu> <14122019722.20010609191234@binity.com> Subject: Re: Re[2]: How to keep a process from eating >n percent CPU? Date: Sat, 9 Jun 2001 13:47:20 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 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 > As a matter of fact I am now using nice(1), I only wished there would be > a means of controlling this in a more "fine-grained" method. For one, I > would love it if I could impose a limit of 90% CPU on Apache, so that if > for example a runaway CGI script started doing weird things, admins > would still have a (greater) possibility to be able to log on the shell > and fix stuff in a proper fashion (i.e. not waiting 30 seconds for the > output of `ps' to appear). That's pretty odd. What are you nicing it to? I've found that nicing things very high will instantly transfer processor power to other processes that need it, no matter how much the runaway process is using. Try using a higher nice value and see if it allows quicker response when things get hairy. -Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message