DebianThis forum is for the discussion of Debian Linux.
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.
For some reason after the computer is on and idle for a little while, xorg starts using all available CPU resources. When I come back to use the computer, the screensaver will either be running nice and smooth, or the screen will be black. Either way, I won't be able to get back into X. I'll ctrl+alt+F1 into the console (or ssh if it's still not responsive) and "top" shows me xorg is hogging all the available CPU. I'll kill -3 <xorg> and it the computer will come back to the kdm login screen. What the %^&*??? It's a little irritating. I'm using Bouncing Cows and Seti@home when idle, but both do their job and close when they detect a key press. Even via ssh when I already tried waking up the computer with a key press, it shows the screensaver closed and seti is idle.
I have Debian/Lenny installed with all the latest updates and ATI's driver installed with direct rendering enabled (350fps for the cows, >2000fps for glxgears). FWIW, it's a Dell Inspiron 8600, 1.8GHz, 2GB Ram, 80GB HD, ATI 9600pro/128MB.
I used to have this issue back when Etch was in testing. Turns out it was caused when SuperKaramba was monitoring my hard drives. I had set a script to kill and restart SuperKaramba every 30 minutes to avoid the issue. Also, at one time, leaving an open bestbuy.com window in Iceweasel also caused this. In both cases, using 'top' only showed it was Xorg using all my CPU power, and not the programs that were actually causing the issue. Chances are, you have something running under X that is causing this, but I'm not sure if you can use 'top' or another app to pinpoint the issue.
If I have IceWeasel open and X appears unresponsive, it really isn't.
Mouse motion still operates, but button clicks do not.
I can type and use keyboard controls to navigate the browser, open and close tabs, but if I close the browser, it just sits there dead.
I can ctrl+alt+Fx and switch freely back and forth between console and X, but the active window's title bar is solid black and will not drag or resize.
I can kill kmail, firefox-bin, & Xorg signal 3 (in that order) and everything is saved and I get back to the KDM login screen.
I log back in and everything runs fine for an unknown amount of time, but at some point, after I walk away for a little while, it acts screwy again.
I try to keep up on all the updates (synaptic manager) but it still keeps happening. Did I mention I'm using KDE 3.5.10 on Debian Lenny?
So my system has been somewhat stable for a couple days now. Apparently rsyslogd was logging every time my Superkaramba theme sudo' for SMART status, but mainly hard disk temperature. All successful pollings were logged to auth.log and would eventually fill up the /var partition causeing issues with running programsn. I edited the rsyslogd.conf file and comented out the auth.log section and resarted rsyslogd. It has been fine ever since.
I'd rather not have the auth disable, but I don't need it to log all successful sudos. Is there some way I can log only unsuccessful to auth.log? For my system it's more valuable to see failed attempts.