Aha! So I'm not going crazy (or if I am, at least this isn't proof of it!)
I'll reserve judgement. You video problem could be because of the way
you treat your monitor ;-)
I've seen similar problems, only on my home machine. Running
KDE, with GOBS and GOBS of memory (256MB), lots of
Thanks Karl.
That's good info.
Paul W
On Tue, 8 Feb 2000, Karl J. Runge wrote:
Hi Paul,
I believe the standard philosophy is that if machine isn't utilizing
(in some way) nearly 100% of the RAM then it is wasting the RAM.
I agree with this for the most part.
So it caches files,
Hi Paul,
I believe the standard philosophy is that if machine isn't utilizing
(in some way) nearly 100% of the RAM then it is wasting the RAM.
I agree with this for the most part.
So it caches files, buffers i/o, and keeps other "slow" data in the
RAM for quick access should the need for them
On Tue, 8 Feb 2000, Kenneth E. Lussier wrote:
Right now, Top reports X as using 31.7% of my memory and 2.6% of my CPU.
What's the Resident Segment Size of X? Not the Virtual Segment Size, mind
you. I believe X maps the video controller into virtual memory, plus who
knows what else, so VSS
On Tue, 8 Feb 2000, Kenneth E. Lussier wrote:
If that doesn't work, you can try including "Magic SYSRQ Keys"
into your kernel.
So THAT'S what that is for I never did get around to reading the
docs on that...
Yup. I've become quite adept at killing X, resetting the keyboard,
On Tue, 8 Feb 2000, Kenneth E. Lussier wrote:
I've been having the same problems ever since RH6.1. Right now, Top
reports X as using 31.7% of my memory and 2.6% of my CPU. If I run a WM
that is resource-intensive (such as KDE, Gnome, E, etc.), there have
been a few occasioins where my whole
