lkml.org 
[lkml]   [1998]   [Nov]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Stopping CPU Hogs...
Tuukka Toivonen wrote:
>
> On Wed, 4 Nov 1998, John Fulmer wrote:
>
> Instead netscape probably sends so fast X messages to the X server that it
> halts, not Linux, but X-server. I think the correct solution (besides
> fixing netscape) would be to fix X-server.

That may be true. However, I have had other (mostly ill behaved) non-x
applications that suck 100%cpu and bring the system to a halt, or at
least make it extremely jerky. This is much more noticeable on my older
K5 than on my newer machines.

Anyway, my question has been answered: No, there is no way to control
the amount of CPU that a single process can suck, except for the kernel
scheduler, and trying to NICE a process.

Thanks for the replies...



--
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ John Fulmer | "UNIX was not designed to stop +
+ Secure Network System | you from doing stupid things, +
+ Lawrence, Kansas | because that would also stop you +
+ | from doing clever things." +
+ jfulmer@iegroup.com | +
+ http://www.iegroup.com | -- Larry Wall +
+ "The opinions contained above may not reflect those of SNS" +
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:45    [W:1.178 / U:1.088 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site