Roy J. Tellason wrote:
On Saturday 25 March 2006 05:08 pm, Don Y wrote:
I think you will find the "packages" to
be of more dubious quality
than the core OS features. There seems to be much less discipline
there. And, I have found people don't often understand what they
are tinkering with as they patch the code -- "it compiled without
any errors, so it MUST be OK, right??" :<
KDE seems to be the one area of the stuff I run here that gives me a bit of
trouble...
Not surprising -- when you look at how BIG it is. :-(
Maybe it's because I'm running several
machines here that never get turned
off. I seldom log off, either. And on this one box (that I'm typing on) I
have continuing increase of swap used, until it gets to the point where
response starts to suffer. Depending on what I'm doing, this can take a few
days, or it can take a few weeks. Running a lot of tasks or a lot of tabs
in the Firefox browser seems to make it worse quicker.
Can you say memory leak? Thought so...
Yup. Hence my analogy to "hammer with dental floss dispenser". :-(
I don't run a "desktop". Just bare xterms/emacs on top of twm.
I don't need much more that that to write/compile/test my code. :>
I keep a disposable Windows machine to talk to the outside world.
Nothing of value on it (software or data) so *if* I encounter
something mean and nasty while online, I just reinsert the CD
and reinstall the OS from scratch. Much less maintenance
required than having to download and apply the newest set of
"security patches" for <fill-in-the-blank> OS. (And, a lot
more peace of mind knowing my codebase is never vulnerable!)
But I don't have to reboot or shut the machine
down or anything like that to
fix it, just log out of KDE and go back in again. Hm, I just looked and
I'm currently up over 207M of swap used, but if I log out of here and log
back in with exactly the same mix of applications open it'll be sitting there
at 3-5M of swap used.
I hope they get it fixed sometime soon...
And, that the fix doesn't break something that you can't work around!
:-(