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.
* Read the Fedora release notes on how to forcefully disable APM and ACPI. See if that changes anything.
* Log in using some remote shell (ssh or telnet) and run 'top' for a while to see what launches or uses large amounts of CPU - around the time you might expect this odd behavior.
* Look into '/var/log/messages' to see if there is any extra information there.
* Try booting into runlevel 3 only (no X-server) and see if changes.
* Try a newer (or older kernel) - NOTE however that this may make things worse - sometimes.
Some problems I've had in the past (which are probably totally unrelated, but just some ideas).
* Faulty BIOS which would put the computer into a odd state.
* A X-server problem which would somehow run away, ignore input and lock all input/output -- BUT the network would still work.
What you said here:
"* A X-server problem which would somehow run away, ignore input and lock all input/output -- BUT the network would still work"
seems to actually be relevant.
I get to work this morning and I can't vnc to the box--but it seems like the network card is working-i have an Apache server running on the box in question which had obviously been accepting connections from clients on our LAN. (i could see this from last logins). Did you work out how to solve the X-server problem?
As for running in level 3-would this disable apache/Mysql?
I never found the exact root cause of the problem. I had some varying success after upgrading both the bios and kernel on the system. Which may have had nothing to do with it, but reduced the problem. In the end, I guessed it was poor chipset on the motherboard and replaced the motherboard. Since then, I've never had the problem.
Using runlevel 3 will not prevent apache/mysql. Just make sure they are both enabled for runlevel 3 and 5:
# chkconfig --level 35 httpd on
# chkconfig --level 35 mysqld on
Thanks guys. Checking now.
Now if this is a server and not a notebook--there shouldn't be any reason to have the apmd daemon running, should there? I can't see why it is--I didn't set it to run on install and don't remember turning it on so I'm guessing it runs by default.