diff options
| author | ddomingo <ddomingo@redhat.com> | 2008-11-04 12:50:46 +1000 |
|---|---|---|
| committer | ddomingo <ddomingo@redhat.com> | 2008-11-04 12:50:46 +1000 |
| commit | bbd2860f9c95fbef790a2f414c8fc6548c5fec3d (patch) | |
| tree | 6ea1ba50a9a960f656513bfb884bc3dd9e153256 /doc/SystemTap_Beginners_Guide | |
| parent | 2dd045b6dfbe200b1b765cf64c7fcd3036a2e87a (diff) | |
| download | systemtap-steved-bbd2860f9c95fbef790a2f414c8fc6548c5fec3d.tar.gz systemtap-steved-bbd2860f9c95fbef790a2f414c8fc6548c5fec3d.tar.xz systemtap-steved-bbd2860f9c95fbef790a2f414c8fc6548c5fec3d.zip | |
added notes and questions to several XMLs
Diffstat (limited to 'doc/SystemTap_Beginners_Guide')
3 files changed, 6 insertions, 0 deletions
diff --git a/doc/SystemTap_Beginners_Guide/en-US/Useful_Scripts-disktop.xml b/doc/SystemTap_Beginners_Guide/en-US/Useful_Scripts-disktop.xml index 041a4689..028ab530 100644 --- a/doc/SystemTap_Beginners_Guide/en-US/Useful_Scripts-disktop.xml +++ b/doc/SystemTap_Beginners_Guide/en-US/Useful_Scripts-disktop.xml @@ -42,7 +42,9 @@ <listitem><para><computeroutput>BYTES</computeroutput> — the amount of data read to or written from disk.</para></listitem> </itemizedlist> +<para>The time and date in the output of <xref linkend="scriptdisktop"/> is returned by the functions <command>ctime()</command> and <command>gettimeofday_s()</command>. <command>ctime()</command> derives calendar time in terms of seconds passed since the Unix epoch (January 1, 1970). <command>gettimeofday_s()</command> counts the <emphasis>actual</emphasis> number of seconds since Unix epoch, which gives a fairly accurate human-readable timestamp for the output.</para> +<remark>needinfo: what does $return do?</remark> <example id="disktopoutput"> <title><xref linkend="scriptdisktop"/> Sample Output</title> <screen> diff --git a/doc/SystemTap_Beginners_Guide/en-US/Useful_Scripts-iotop.xml b/doc/SystemTap_Beginners_Guide/en-US/Useful_Scripts-iotop.xml index 4fd41c6e..6742740f 100644 --- a/doc/SystemTap_Beginners_Guide/en-US/Useful_Scripts-iotop.xml +++ b/doc/SystemTap_Beginners_Guide/en-US/Useful_Scripts-iotop.xml @@ -16,6 +16,8 @@ </para> </formalpara> +<remark>what does $count do, specifically?</remark> + <para><xref linkend="iotop"/> prints out the top ten executables generating I/O traffic every 5-second interval, in descending order. Its output contains the process name and the amount of data read or written by the process, in KB. For example:</para> <example id="iotopoutput"> diff --git a/doc/SystemTap_Beginners_Guide/en-US/Useful_Scripts-traceio.xml b/doc/SystemTap_Beginners_Guide/en-US/Useful_Scripts-traceio.xml index 71bd1984..14dc754c 100644 --- a/doc/SystemTap_Beginners_Guide/en-US/Useful_Scripts-traceio.xml +++ b/doc/SystemTap_Beginners_Guide/en-US/Useful_Scripts-traceio.xml @@ -17,6 +17,8 @@ </para> </formalpara> +<remark>what do $return, $length, and $count return, specifically? when i substituted $return for $length here, script still ran but gave me bigger numbers. errored out with $length. where documented?</remark> + <para><xref linkend="traceio"/> is similar to <xref linkend="iotop"/> (from <xref linkend="iotopsect"/>); both SystemTap scripts print out the top ten executables generating I/O traffic over time. However, <xref linkend="traceio"/> tracks the <emphasis>cumulative</emphasis> amount of I/O reads and writes done by the system's top ten executables. This information is tracked and printed out in 1-second intervals and in descending order.</para> <example id="traceiooutput"> |