![]() |
FAQ.HowtoIdentifyWhichProcessesAccessDisk HistoryHide minor edits - Show changes to markup July 06, 2007, at 01:59 PM
by -- removed false wikilinks
Changed lines 55-56 from:
In OpenDebianSlug? you don't get 'lm-profiler' even if you install laptop-mode-tools using apt-get. Do the following in OpenDebianSlug?: to:
In OpenDebianSlug you don't get 'lm-profiler' even if you install laptop-mode-tools using apt-get. Do the following in OpenDebianSlug: July 06, 2007, at 01:57 PM
by -- problem - no block_dump on 6.8...
Added lines 33-34:
March 11, 2007, at 02:16 AM
by --
Changed lines 7-9 from:
Spinup Debugging to:
Spinup DebuggingMarch 11, 2007, at 02:15 AM
by --
Changed line 17 from:
Busybox syslog.confto:
Busybox syslog.confChanged line 22 from:
Syslog.confto:
Syslog.confMarch 11, 2007, at 02:14 AM
by --
Changed line 17 from:
Busybox syslog.confto:
Busybox syslog.confChanged line 22 from:
Syslog.confto:
Syslog.confChanged line 26 from:
Turn on disk activity debugging/to:
Turn on disk activity debuggingMarch 11, 2007, at 02:14 AM
by --
Changed line 17 from:
Busybox syslog.conf\to:
Busybox syslog.confChanged line 22 from:
Syslog.conf\to:
Syslog.confMarch 11, 2007, at 02:14 AM
by --
Changed line 17 from:
Busybox syslog.conf/to:
Busybox syslog.conf\Changed line 22 from:
Syslog.conf/to:
Syslog.conf\March 11, 2007, at 02:13 AM
by --
Added lines 13-22:
How you modify syslog.conf depends on which syslogd is installed. If your '/sbin/syslogd' is a symbolic link to 'busybox' then you really don't have a fully functional syslogd and should follow the 'Busybox syslog.conf' instructions. Everyone else should follow the 'syslog.conf' instructions. Busybox syslog.conf/First stop the syslogd with the command '/etc/init.d/syslog stop' Then edit '/etc/syslog.conf' and Change the 'DESTINATION' to 'buffer' Restart the syslogd with the command '/etc/init.d/syslog start' Syslog.conf/Changed lines 24-25 from:
to:
You then have to either 'kill -HUP' on the syslogd process or start and stop the daemon. Turn on disk activity debugging/March 11, 2007, at 01:59 AM
by --
Changed lines 13-15 from:
In syslog.conf, you have to place a dash (-) before the log file name, e.g. the line kern.* /var/log/kern.log becomes kern.* -/var/log/kern.log. to:
In /etc/syslog.conf, you have to place a dash (-) before the log file name, e.g. the line kern.* /var/log/kern.log becomes kern.* -/var/log/kern.log. Deleted line 17:
March 11, 2007, at 01:56 AM
by --
Changed lines 12-14 from:
Yes, you can. But first, check that you have modified your syslog.conf to not sync, as described in the next question. To debug disk activity, you can do: to:
Yes, you can. But first, check that you have modified your syslog.conf to not sync. In syslog.conf, you have to place a dash (-) before the log file name, e.g. the line kern.* /var/log/kern.log becomes kern.* -/var/log/kern.log. Then to debug disk activity, you can do: March 07, 2007, at 05:50 PM
by --
Added line 42:
Added line 44:
Added line 46:
March 07, 2007, at 05:49 PM
by -- Added info on how to use lm-profiler in OpenDebianSlug
Added lines 36-45:
In OpenDebianSlug? you don't get 'lm-profiler' even if you install laptop-mode-tools using apt-get. Do the following in OpenDebianSlug?: cd /root wget http://samwel.tk/laptop_mode/tools/downloads/laptop-mode-tools_1.31.tar.gz tar -xzvf laptop-mode-tools_1.31.tar.gz ./laptop-mode-tools-1.31/usr/sbin/lm-profiler January 22, 2007, at 07:14 AM
by -- Updated link to Laptop Mode Tools FAQ
Changed lines 5-6 from:
(From http://www.xs4all.nl/~bsamwel/laptop_mode/tools/faq.html) to:
(From http://www.samwel.tk/laptop_mode/tools/faq.html) August 10, 2006, at 07:09 PM
by -- Link to an existing page that contains much of this information
Added lines 1-2:
See also the existing page, IdentifyWhichProcessesAccessDisk August 10, 2006, at 12:02 PM
by -- typos
Changed lines 1-2 from:
To find out which processes spins up your disk, do this: to:
To find out which process spins up your disk, do this: Changed lines 27-28 from:
This package contains a set of scripts which monitor your harrdisk (it could set several energy saving profiles too but the NSLU2 doesnt support this). to:
This package contains a set of scripts which monitor your hardisk (it could set several energy saving profiles too but the NSLU2 doesnt support this). August 10, 2006, at 10:08 AM
by -- LM-Profiler and Blockdump
Added lines 1-33:
To find out which processes spins up your disk, do this: (From http://www.xs4all.nl/~bsamwel/laptop_mode/tools/faq.html) Spinup Debugging My disk spins up all the time and I have no clue what causes this. Can I debug this? Yes, you can. But first, check that you have modified your syslog.conf to not sync, as described in the next question. To debug disk activity, you can do: echo 1 > /proc/sys/vm/block_dump (Warning: you must disable syslogd before you do this, or you must make sure that kernel output is not logged. If you forget this, your system may get into a feedback loop, where syslogd causes disk activity, this causes kernel output, and this causes syslogd to do more disk activity, etcetera!) This enables file/disk activity debugging in the kernel. You can read the output using dmesg. When you're done, disable block dump using echo 0 > /proc/sys/vm/block_dump Under debianslug it is easier to accomplish. Simply install laptop-mode-tools aptitude install laptop-mode-tools This package contains a set of scripts which monitor your harrdisk (it could set several energy saving profiles too but the NSLU2 doesnt support this). The most interesting script is called lm-profiler. Start it with lm-profiler and watch it's output. It lets you disable unneeded system services after the scan too if you want. |