Leftover changes from the past.

TODO

@@ -15,6 +15,7 @@ contact me as well. :) Send an email to: Dag Wieers <dag@wieers.com>
 + Allow to force to given magnitude (--unit=kilo)
 + Look at possibilities to show deviation (on second line ?)
 + Check for dark/light background color and change colors accordingly (see dstat.conf)
++ Show parts of counters in other colors (eg. color the 6 in 6134B in yellow to indicate it's kilobyte)
 
 ### Export/Graph
 + Interface with rrdtool (python-rrd ?)
@@ -40,6 +41,7 @@ contact me as well. :) Send an email to: Dag Wieers <dag@wieers.com>
   (explaining the different values in /proc, especially the concerning ones)
 + Create document on general system performance tools
   (explaining the different uses of tools like dstat, iostat, pmap, strace, tcpdump)
++ Comply to PEP8: http://www.python.org/dev/peps/pep-0008/
 
 ### General issues
 + Timer is not as accurate on 2.6 kernel as on 2.4, possibly scheduling differences

docs/dstat.1.txt

@@ -1,7 +1,7 @@
 dstat(1)
 ========
 Dag Wieers <dag@wieers.com>
-v0.6.3, Juni 2006
+v0.6.3svn, Juni 2006
 
 
 NAME
@@ -111,13 +111,13 @@ OPTIONS
 	enable unix stats
 
 -M stat1,stat2::
-	enable internal and external stats
+	enable internal stats and external plugin stats
 
 Possible internal stats are::
   cpu, cpu24, disk, disk24, disk24old, int, int24, ipc, load, lock, mem,
   net, page, page24, proc, raw, swap, swapold, sys, tcp, time, udp, unix
 
-Possible external stats can be listed using::
+Possible external plugin stats can be listed using::
   dstat -M list
 
 -a, --all::
@@ -179,6 +179,11 @@ Checking dstat's behaviour and the system's impact on dstat:::
 dstat -taf --debug
 .....
 
+Using the external clock and app plugins together with normal system resources:::
+....
+dstat -M clock,app -cndylp
+....
+
 
 BUGS
 ----
@@ -194,7 +199,7 @@ Please see the TODO file for known bugs and future plans.
 
 FILES
 -----
-Paths that may contain external dstat_* modules:
+Paths that may contain external dstat_* plugins:
 
 	~/.dstat/
 	./

docs/performance.txt

@@ -35,6 +35,10 @@ Remember that invisible plugins (that run out of your terminal window)
 do take up cycles because the information is still being collected and
 possibly written to CSV output.
 
+It should be possible to write plugins in C to improve the impact on
+the system, but I have no experience with writing python modules in C.
+Any feedback on this is welcomed.
+
 
 Performance tuning
 ------------------

dstat

@@ -1652,9 +1652,9 @@ def signaler(signum, frame):
 	signal.alarm(interval)
 
 def exit(ret):
-	sys.stdout.write(ansi['reset'])
 	if 'signal' in sys.modules.keys():
 		signal.signal(signal.SIGALRM, signal.SIG_DFL)
+	sys.stdout.write(ansi['reset'])
 	sys.exit(ret)
 
 def listmodules():