Hi Guillaume
Thanks for the explanation.
When you compare that to top I must say that my top (part of procps 3.2.8)
/does/ deliver values on the first shot. Even with top -d 3600.
Unfortunately -o doesn't help in my case (to make a long story short: I'm
collecting performance data - and no
two
snapshots taken (or there is no time delay between the both). But that wouldn't
explain the different behaviour on our machines.
Regards,
uwe
-Original Message-
From: Paul Wise [mailto:p...@debian.org]
Sent: Samstag, 26. Februar 2011 06:15
To: Maier, Uwe; 614...@bugs.debian.org
I will be hit
by that bad first line.
The first screen is always wrong btw. Even without -b (e.g. iotop -d60).
Regards,
uwe
-Original Message-
From: Paul Wise [mailto:p...@debian.org]
Sent: Freitag, 25. Februar 2011 04:11
To: Maier, Uwe; 614...@bugs.debian.org
Cc: control
Subject
Hi Paul,
a.) fails here too
b.) fails here
c.) fails here
Seems your system is different than mine (smp?).
Regards,
uwe
-Original Message-
From: Paul Wise [mailto:p...@debian.org]
Sent: Freitag, 25. Februar 2011 10:44
To: Maier, Uwe
Cc: 614...@bugs.debian.org
Subject: RE: Bug
Package: iotop
Version: 0.4-2
Severity: normal
When using the -b parameter which should enable the batch mode every value is
reset to 0.0 .
Adding other parameters like -P, -a, -n, -k do not change anything.
Saving the output of iotop without -b to a file (containing all the control
characters)
5 matches
Mail list logo
