Date: Sat, 9 Jun 2001 19:12:34 +0200 From: Walter Hop <walter@binity.com> To: "Jonathan Slivko" <js43064n@pace.edu> Cc: FreeBSD Questions <freebsd-questions@freebsd.org>, teo@gecadsoftware.com Subject: Re[2]: How to keep a process from eating >n percent CPU? Message-ID: <14122019722.20010609191234@binity.com> In-Reply-To: <200106091245.AA1833238794@stmail.pace.edu> References: <200106091245.AA1833238794@stmail.pace.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Teo and Jonathan, >> lauch it using bash, after you previously imposed a limit on >> resurses with ulimit (in your case, with -t) Unfortunately the limit controls of `ulimit' and in login.conf can only impose a limit on CPU seconds, not percentage. This is good for batch jobs, but not for a daemon, to which I would typically allocate an unlimited amount of CPU time (they could be running for months on end). > Or run it with "nice" =) 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). Thanks for your replies anyway; any further comments would be appreciated :) walter. -- Walter Hop <walter@binity.com> | +31 6 24290808 | Finger for public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?14122019722.20010609191234>