X-Git-Url: http://git.grml.org/?a=blobdiff_plain;f=grml_tips;h=29fa9963917ed0c64bcaf037d22b5504fc427ad8;hb=ec4516da3042ce4f53d5c2c07dbbd957f6801afd;hp=21ff86c6e1d2436cabc884ebde564a81178caabd;hpb=0f7d60b21a1cd14b32a84069fa942ad64ab40e8a;p=grml-tips.git

diff --git a/grml_tips b/grml_tips
index 21ff86c..29fa996 100644
--- a/grml_tips
+++ b/grml_tips
@@ -1756,12 +1756,14 @@ 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?
 
 # 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 +1771,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 +2386,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 +2492,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!