X-Git-Url: http://git.grml.org/?a=blobdiff_plain;f=grml_tips;h=de47abc5eb13d4f42af8af09f5d14c8e24f9f990;hb=refs%2Ftags%2F0.3.26;hp=94a7c974639bfe0263cd32df2a8aafa45ba697bc;hpb=17034dd1db814f3d24e0097e34eedb9e6ba62022;p=grml-tips.git

diff --git a/grml_tips b/grml_tips
index 94a7c97..de47abc 100644
--- a/grml_tips
+++ b/grml_tips
@@ -1756,12 +1756,16 @@ Start X and lock console via exiting:
 
 % startx 2>~/.xsession-errors &| exit
 -- 
-Which process is writing to disk?
+Which process is writing to disk and/or causes the disk to spin up?
+
+First of all use lsof to check what's going on. Does not help? ->
 
 # 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.
+The command sets a sysctl to cause the kernel to log all disk
+writes. Please notice that there is a lot of data.  So please
+disable syslogd/syslog-ng before you do this, or you must make
+sure that kernel output is not logged.
 
 When you're done, disable block dump using:
 # echo 0 > /proc/sys/vm/block_dump
@@ -1769,6 +1773,10 @@ When you're done, disable block dump using:
 Alternative:
 laptop-mode-tools provides a tool named lm-profiler (laptop mode profiler)
 which handles block_dump on its own.
+
+See: $KERNEL-SOURCE/Documentation/laptop-mode.txt
+
+Also take a look at event-viewer(8) which is part of grml-debugtools.
 -- 
 Install initrd via initramfs-tools for currently running kernel:
 
@@ -2380,17 +2388,6 @@ EOF
 Start dnsmasq finally:
 # Restart dnsmasq
 -- 
-Find out which process(es) cause the disk to spin up:
-
-# echo 1 > /proc/sys/vm/block_dump
-
-The command sets a sysctl to cause the kernel to log all disk
-writes. Please notice that there is a lot of data.
-
-See: $KERNEL-SOURCE/Documentation/laptop-mode.txt
-
-Also take a look at event-viewer(8).
--- 
 Display stats about memory allocations performed by a program:
 
 Usage example for 'ls':
@@ -2497,7 +2494,7 @@ Configuration options relevant on harddisk installation:
 * If you change the time (using 'date --set ...', ntpdate,...)
   it is worth setting also the hardware clock to the correct time:
 
-  # hwclock --hctosys [--utc]
+  # hwclock --systohc [--utc]
 
   Remember to add the --utc -option if the hardware clock is set
   to UTC!
@@ -2516,6 +2513,7 @@ Check your current settings via:
 
 Further information:
 --------------------
+
   hwclock(8) tzselect(1) tzconfig(8)
   http://www.debian.org/doc/manuals/system-administrator/ch-sysadmin-time.html
   http://wiki.debian.org/TimeZoneChanges