summaryrefslogtreecommitdiffstats
path: root/lket-b2a.1.in
diff options
context:
space:
mode:
Diffstat (limited to 'lket-b2a.1.in')
-rw-r--r--lket-b2a.1.in44
1 files changed, 22 insertions, 22 deletions
diff --git a/lket-b2a.1.in b/lket-b2a.1.in
index da77f25a..0d8a71b1 100644
--- a/lket-b2a.1.in
+++ b/lket-b2a.1.in
@@ -1,7 +1,7 @@
.\" -*- nroff -*-
-.TH LKET-B2A 1 @DATE@ "IBM"
+.TH LKET\-B2A 1 @DATE@ "IBM"
.SH NAME
-lket-b2a \- Converting and dumping utility for LKET binary trace data
+lket\-b2a \- Converting and dumping utility for LKET binary trace data
.\" macros
.de SAMPLE
@@ -19,7 +19,7 @@ lket-b2a \- Converting and dumping utility for LKET binary trace data
.SH SYNOPSIS
.br
-.B lket-b2a
+.B lket\-b2a
.I OPTIONS
.IR IN_FILENAME ...
.br
@@ -30,22 +30,22 @@ The trace data generated by
.I LKET
is in binary format by default for
better performance and smaller size.
-.I lket-b2a
+.I lket\-b2a
is used to convert the
binary trace data into readable data in ascii format and save
them into local file or MySQL database for off-line trace analysis.
It uses the per-cpu binary trace data files (stpd_cpu*) as inputs.
-You can use "stap -bM" with LKET to get those per-cpu files before using it.
+You can use "stap \-bM" with LKET to get those per-cpu files before using it.
The database used by
-.I lket-b2a
+.I lket\-b2a
is MySQL. So MySQL must be properly installed
and configured in order to make
-.I lket-b2a
+.I lket\-b2a
able to dump the trace data into MySQL database.
.SH OPTIONS
-.I lket-b2a
+.I lket\-b2a
supports the following two options. They can be used
together or alone but at least one of them should be specified:
@@ -60,17 +60,17 @@ See the following section.
.TP
.B \-n
name_flag. name_flag set to 0 means not printing the event
-description string and 1 means printing. Only valid with -f
+description string and 1 means printing. Only valid with \-f
option. name_flag is set to 1 by default.
.TP
.B \-i
id_flag. id_flag set to 0 means not printing event groupid and
-hookid and 1 means printing. Only valid with -f option. id_flag
+hookid and 1 means printing. Only valid with \-f option. id_flag
is set to 0 by default.
.TP
.B \-a
appname_flag. appname_flag set to 0 means not printing process
-name and 1 means printing. Only valid with -f option. appname_flag
+name and 1 means printing. Only valid with \-f option. appname_flag
is set to 1 by default.
.SH DUMP TRACE DATA INTO LOCAL FILE
@@ -80,7 +80,7 @@ The generated output file is named
The following is an example:
.SAMPLE
-root:/home/root/data> lket-b2a -f stpd_cpu*
+root:/home/root/data> lket\-b2a \-f stpd_cpu*
root:/home/root/data> cat lket.out
LKET Magic: 0xAEFCDB6B
InitHdrLen: 9
@@ -91,8 +91,8 @@ Timing method: do_gettimeofday()
Bits width: 64
Initial CPU timebase: 1596405 (cycles per microsecond)
[...]
-2.527880 CPU:0 PID:2450 APPNAME:gnome-panel EVT_NAME:iosyscall.read.entry fd:3,buff_addr:-1081126904,count:32,
-2.527887 CPU:0 PID:2450 APPNAME:gnome-panel EVT_NAME:iosyscall.read.return return:32,
+2.527880 CPU:0 PID:2450 APPNAME:gnome\-panel EVT_NAME:iosyscall.read.entry fd:3,buff_addr:\-1081126904,count:32,
+2.527887 CPU:0 PID:2450 APPNAME:gnome\-panel EVT_NAME:iosyscall.read.return return:32,
2.534343 CPU:0 PID:1450 APPNAME:kjournald EVT_NAME:scsi.ioentry major:8,minor:0,sdev_state:2,request_addr:3806880208,
2.534359 CPU:0 PID:1450 APPNAME:kjournald EVT_NAME:scsi.iodispatching host:0,channel:0,lun:0,dev_id:0,dev_state:2,data_dir:1,reqbuf_addr:3248315840,reqbuf_len:8192,request_addr:3806880208,
[...]
@@ -103,28 +103,28 @@ Initial CPU timebase: 1596405 (cycles per microsecond)
To avoid either reading the complete trace data into internal data
structures to process, or filter through the raw trace data again
and again to calculate the interesting metrics,
-.I lket-b2a
+.I lket\-b2a
supports convert and save the binary trace data into MySQL database to
facilitate the query and calculation on the trace data.
-.I lket-b2a
+.I lket\-b2a
creates the database name based on current time. And
-.I lket-b2a
+.I lket\-b2a
will not only save the trace data, but also some meta data into MySQL
database too, such as trace header, trace table description.
The following is an example of navigating the trace data in MySQL database
created by
-.IR lket-b2a :
+.IR lket\-b2a :
Use
-.I lket-b2a
+.I lket\-b2a
to convert and dump the binary trace data of
.I LKET
into MySQL database:
.SAMPLE
-root:/home/root/data> lket-b2a -m stpd_cpu*
+root:/home/root/data> lket\-b2a \-m stpd_cpu*
.ESAMPLE
list all databases in MySQL:
@@ -141,7 +141,7 @@ mysql> show databases;
3 rows in set (0.00 sec)
.ESAMPLE
-DB20061023161626 is the newly created database by "lket-b2a -m stpd_cpu*". We can list
+DB20061023161626 is the newly created database by "lket\-b2a \-m stpd_cpu*". We can list
all the tables contained in DB20061023161626:
.SAMPLE
@@ -239,7 +239,7 @@ named
for all return type event tables which is the timestamp
of the entry of that event. The column
.I entry_usec
-is created and calculated by lket-b2a on the fly while processing the binary trace data.
+is created and calculated by lket\-b2a on the fly while processing the binary trace data.
.SAMPLE
mysql> select * from 2_1 limit 4;