Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Hi, i have redhat 8.0 and im using KDE. I was expecting it not to crash, or at least very rarely, but in the last week or so, it has crashed about 3 times.
The latest crash was when i woke up this morning, i left my computer on over night, got up, ran mozilla and everything stopped. I left it for quite a while incase it was doing something, but nothing happened. Is this normal? Is there any steps i can take to find out why it crashed, and how to prevent it?
ok its happened twice since. one time i woke up, tried to run the konsole, and as i clicked the button my computer completely froze. the other time it froze sometime in the night and i woke up to a frozen screensaver.
the only common things between all the crashes in the screensaver and KDE. i will try turning off the screensaver to see if it stops this from happening. has anyone got any other ideas as to why this might be happening?
At first, my favourite window manager is KDE.
But I've come across some crashes like that in redhat 8.0. Then I changed to GNOME and i find that it's more stable and faster too. Gnome is very much improved in Redhat 8.0. (I mean the version of gnome in redhat 8.0)
You may want to try Gnome.
Last edited by moeminhtun; 01-15-2003 at 01:45 AM.
btw if anyone reading this is thinking of getting linux and is put off by my problem, dont be. to prove the stability of linux, i went to an idiots website who opened up 150 pop-up windows on my computer. linux merriily opened them all, and loaded the pages up without moaning to me about insuffient memory or anything, and i was even able to continue using my second desktop and not notice any system lag. closed them all down, and everything is fine. a little while ago i managed to open about 50 windows in windows xp (on the same machine) before it started to moan about a lack of system resources, and i had to reboot to be able to use my computer again cos it was bogged down so much. so to summarise - linux is cool.
Distribution: Red Hat (8.0, RHEL5,6), CentOS, SuSE (10.x, 11.x, 12.2, 13.2), Solaris (8-10), Tru64, MacOS, Raspian
Originally posted by MasterC
If this doesn't help, try starting "top" before you go to bed, leave it running all night, then whenever it crashes, hopefully at the top of the list will be some suspect hoggin all your resources
Trouble with that is that `top' is mainly CPU oriented (AFAIK, being able to sort by memory usage is a fairly new feature). It sure would be nice to have it be able to sort the processes list by biggest I/O users, who's causing the most page faults, etc. Instead, I'd suggest writing a quick-n-dirty shell script that runs `ps auwx' and `/sbin/swapon -s' every couple minutes and which writes its output to a file. Heck, you could even just stick the command `( ps auwx ; /sbin/swapon -s ) > /tmp/system_status.lis' directly in your crontab. (Can't get much quicker or dirtier than that.) Then after a crash you have some evidence of what was running when the system went down.
I'd be inclined to agree with the poster who suggested that Mozilla was probably the culprit. But I've never seen it hang X when it was unattended. Wonder if the original postier was running anything like gkrellm that'll let you see your swap utilization. Running out of swap is possible if you get large number of browser windows open at the same time. Though, 50 doesn't seem like such a large number. I think I was able to get around 250 open once before the system became pretty much unusable. (One of those ``I wonder what happens if you...'' experiments.)