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.
Just broke my Linux cherry (yeah, yeah - so, I'm a late bloomer), and installed Woody (3.0r3) Non-US, on a PII 333MHz generic box w/ 512MB, and a 6GB disk.
After having a problem getting X up using a Diamond Stealth 64 DRAM card, a quick swap out to a slightly newer STB Velocity 4400 w/ RivaTNT, and things are golden. This is pretty nice stuff, folks!
Before heading on to update, and install other toys like firewall, mozilla etc, there is a nuisance that needs fixing.... and, hopefully someone here has a quick clue.
System boots fine, xdm fires up, I log in and have a very snazzy KDE desktop. Woo-hoo!
While my gleaming new little 'nix box is sitting 'idle', and I'm playing on another system trying to concentrate on other matters, like RTFM'ing, the Debian box happily hits its system disk.... every 10-11 seconds. Like a little kid whacking a drum needing attention. Brrrrrrrrrrt-chuck! Brrrrrrrrrrt-chuck!
Firing up kpm to see who's doing what, it appears based on cpu usage, that klipper is the fella waking up to do stuff... whatever that is. Any suggestions as to how to silence my little beastie, or pursue it?
Ok, first of all, you don't want to go killing random processes. That's pretty much a universal rule regardless of what OS you use. If you're not sure about something, look it up on Google (start with queries akin to debian klipper, linux kicker, etc).
Incidentally, Kicker is KDE's panel application and Klipper its clipboard app; you don't want to kill either one.
As for visually determining what is actually causing those disk accesses... there doesn't seem to be any tool that will allow you to do just that. My guess is that it's benign; swapping, file system journalling, the "update" process syncing the disk(s) periodically, etc.
However, it is possible that it's not harmless. Connecting a fresh installation of Debian to a network without stopping various network services or enabling a firewall is a great way to get your box compromised very quickly. Rule that out first, then when you know more about Debian and Linux, go hunting for the cause of those annoying disk accesses.
Originally posted by CritterZ While my gleaming new little 'nix box is sitting 'idle', and I'm playing on another system trying to concentrate on other matters, like RTFM'ing, the Debian box happily hits its system disk.... every 10-11 seconds. Like a little kid whacking a drum needing attention. Brrrrrrrrrrt-chuck! Brrrrrrrrrrt-chuck!
Welcome to Linux. You won't regret it
I assume it's the harddisk making the sound... There is a tool that will give you details about what processes are access the disk, but the name has slipped my mind. Maybe someone else knows.
On the top of my head, it could be two things.
1) The commit-interval for your filesystem. Journaling filesystems frequenly do some disk-activity to be able to recover in the event of something weird happening. The commit-interval can be changed with a mount parameter, these are specified in /etc/fstab. One way to test it could be to umount one partition (asuming you don't have everything in one mount-point) and then remount it with a different commit-interval.
2) Something is causing a something to be written to a log file. Check /var/log/syslog and/or /var/log/messages and the timestamps there. I had the "problem" of my firewall logging stuff there, and at the same time my Windows box (connected to the same network) sending strange packages on the network...
Hope this may give you a starting point at least...