MBMarduk
01-07-2001, 08:36 PM
It's been the 4th time in about 3 weeks. I got SuSE 6.4...
I run KDE and X 3.3.6 with my user-account.
Then I run an app. (something like a graphic KDE-app. I ran two different ones. the same sh*t happens.)
Here's what happens: When you quit, my HDD starts searching/writing/reading... anyway it goes wild and stays that way for hours on end and I cant do CTRL-ALT-Fx to go to the CLI. I also can't move the mouse. CTRL-ALT-DEL doesn't do anything. In short NOTHING WORKS.
***
The lock-up also occured without HDD activity when in KFM I clicked on a shell-script that (I forgot) would ask for SU confirmation to uninstall Opera.
***
Had to reset my box and use a rescue CD to e2fsck each of the 4 times.
***
My question: can I set anything with 'ulimit'
so KDE doesn't gobble up all my resources when jamming? That way (...I think) I could CTRL-ALT-F1 to the Root-CLI and kill -9 the GUI piece by piece.
But I read the manpage and can't figure out what parameters to set.
What's STACK? (I know the name since 1988, but not what exactly it means.)
What's VIRTUAL MEM? (Is it SWAP+REAL MEM?)
What's CORE FILES?
What's PROCESS DATA-SEGMENT?
What's PIPE SIZE?
How do you know how much CPU-time to assign to a process?
PHEEwww...
If anyone could redirect my questions or answer them directly I would learn a lot of Linux and be eternally grateful...
-Mike
P.S. I saw a similar posting in http://www.linuxnewbie.org/ubb/Forum4/HTML/003152.html , but I don't know how to repost messages.
I run KDE and X 3.3.6 with my user-account.
Then I run an app. (something like a graphic KDE-app. I ran two different ones. the same sh*t happens.)
Here's what happens: When you quit, my HDD starts searching/writing/reading... anyway it goes wild and stays that way for hours on end and I cant do CTRL-ALT-Fx to go to the CLI. I also can't move the mouse. CTRL-ALT-DEL doesn't do anything. In short NOTHING WORKS.
***
The lock-up also occured without HDD activity when in KFM I clicked on a shell-script that (I forgot) would ask for SU confirmation to uninstall Opera.
***
Had to reset my box and use a rescue CD to e2fsck each of the 4 times.
***
My question: can I set anything with 'ulimit'
so KDE doesn't gobble up all my resources when jamming? That way (...I think) I could CTRL-ALT-F1 to the Root-CLI and kill -9 the GUI piece by piece.
But I read the manpage and can't figure out what parameters to set.
What's STACK? (I know the name since 1988, but not what exactly it means.)
What's VIRTUAL MEM? (Is it SWAP+REAL MEM?)
What's CORE FILES?
What's PROCESS DATA-SEGMENT?
What's PIPE SIZE?
How do you know how much CPU-time to assign to a process?
PHEEwww...
If anyone could redirect my questions or answer them directly I would learn a lot of Linux and be eternally grateful...
-Mike
P.S. I saw a similar posting in http://www.linuxnewbie.org/ubb/Forum4/HTML/003152.html , but I don't know how to repost messages.