1TRACE-CMD-SPLIT(1)              [FIXME: manual]             TRACE-CMD-SPLIT(1)
2
3
4

NAME

6       trace-cmd-split - split a trace.dat file into smaller files
7

SYNOPSIS

9       trace-cmd split [OPTIONS] [start-time [end-time]]
10

DESCRIPTION

12       The trace-cmd(1) split is used to break up a trace.dat into small
13       files. The start-time specifies where the new file will start at. Using
14       trace-cmd-report(1) and copying the time stamp given at a particular
15       event, can be used as input for either start-time or end-time. The
16       split will stop creating files when it reaches an event after end-time.
17       If only the end-time is needed, use 0.0 as the start-time.
18
19       If start-time is left out, then the split will start at the beginning
20       of the file. If end-time is left out, then split will continue to the
21       end unless it meets one of the requirements specified by the options.
22

OPTIONS

24       -i file
25           If this option is not specified, then the split command will look
26           for the file named trace.dat. This options will allow the reading
27           of another file other than trace.dat.
28
29       -o file
30           By default, the split command will use the input file name as a
31           basis of where to write the split files. The output file will be
32           the input file with an attached ´.#\´ to the end: trace.dat.1,
33           trace.dat.2, etc.
34
35               This option will change the name of the base file used.
36
37               -o file  will create file.1, file.2, etc.
38
39       -s seconds
40           This specifies how many seconds should be recorded before the new
41           file should stop.
42
43       -m milliseconds
44           This specifies how many milliseconds should be recorded before the
45           new file should stop.
46
47       -u microseconds
48           This specifies how many microseconds should be recorded before the
49           new file should stop.
50
51       -e events
52           This specifies how many events should be recorded before the new
53           file should stop.
54
55       -p pages
56           This specifies the number of pages that should be recorded before
57           the new file should stop.
58
59               Note: only one of *-p*, *-e*, *-u*, *-m*, *-s* may be specified at a time.
60
61               If *-p* is specified, then *-c* is automatically set.
62
63       -r
64           This option causes the break up to repeat until end-time is reached
65           (or end of the input if end-time is not specified).
66
67               trace-cmd split -r -e 10000
68
69               This will break up trace.dat into several smaller files, each with at most
70               10,000 events in it.
71
72       -c
73           This option causes the above break up to be per CPU.
74
75               trace-cmd split -c -p 10
76
77               This will create a file that has 10 pages per each CPU from the input.
78

SEE ALSO

80       trace-cmd(1), trace-cmd-record(1), trace-cmd-report(1),
81       trace-cmd-start(1), trace-cmd-stop(1), trace-cmd-extract(1),
82       trace-cmd-reset(1), trace-cmd-list(1), trace-cmd-listen(1)
83

AUTHOR

85       Written by Steven Rostedt, <rostedt@goodmis.org[1]>
86

RESOURCES

88       git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/trace-cmd.git
89

COPYING

91       Copyright (C) 2010 Red Hat, Inc. Free use of this software is granted
92       under the terms of the GNU Public License (GPL).
93

NOTES

95        1. rostedt@goodmis.org
96           mailto:rostedt@goodmis.org
97
98
99
100[FIXME: source]                   03/23/2017                TRACE-CMD-SPLIT(1)
Impressum