[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-commits
Subject:    kdebase/kicker/applets/naughty
From:       CVS by rikkus <kde-cvs () kde ! org>
Date:       2001-01-04 0:17:20
[Download RAW message or body]


kdebase/kicker/applets/naughty .cvsignore,NONE,1.1 Makefile.am,NONE,1.1 \
NaughtyApplet.cpp,NONE,1.1 NaughtyApplet.h,NONE,1.1 NaughtyConfigDialog.cpp,NONE,1.1 \
NaughtyConfigDialog.h,NONE,1.1 NaughtyProcessMonitor.cpp,NONE,1.1 \
NaughtyProcessMonitor.h,NONE,1.1 naughty-happy.png,NONE,1.1 naughty-sad.png,NONE,1.1 \
                naughtyapplet.desktop,NONE,1.1
Author: rikkus
Thu Jan  4 00:17:19 UTC 2001
In directory cvs.kde.org:/tmp/cvs-serv14906

Added Files:
	.cvsignore Makefile.am NaughtyApplet.cpp NaughtyApplet.h 
	NaughtyConfigDialog.cpp NaughtyConfigDialog.h 
	NaughtyProcessMonitor.cpp NaughtyProcessMonitor.h 
	naughty-happy.png naughty-sad.png naughtyapplet.desktop 
Log Message:
A new applet that catches runaway processes and offers to stop them.

You can tell it to ignore certain processes. If you elect to ignore
a process that's eating CPU (e.g. cc1plus) then it asks if you want
to ignore it in future.

You can edit the list of process names to ignore.

It works with kdeinit-wrappered processes.

You can set the interval between updates.

You can set the CPU load that triggers a warning.

It uses ~0 CPU most of the time - until CPU load is high, when it
uses a small amount as it figures out which processes are eating
the CPU.

Currently only works on Linux, but it's very simple to port it to
other OSes. It should be obvious when reading NaughtyProcessMonitor.cpp
where to add code.

It is compiled on every system, but on anything but Linux, it just
sits there and smiles stupidly at you.

It could do with a better 'face' - but I think it's ok for now.

Feel free to enhance it.

This is going into CVS as a test. It works for me (tm) and I think
it might be very useful for our users. For developers, it might
be irritating to have to click a couple of buttons every so often
to tell it that you don't want it to cry when you're compiling,
but I still think it's worth it. It doesn't bother me anymore -
except when I have a runaway process. That means it works :)


[prev in list] [next in list] [prev in thread] [next in thread]