Commit | Line | Data |
---|---|---|
30ec772c PP |
1 | lttng-start(1) |
2 | ============== | |
4605890e | 3 | :revdate: 7 April 2016 |
30ec772c PP |
4 | |
5 | ||
6 | NAME | |
7 | ---- | |
8 | lttng-start - Start LTTng tracers | |
9 | ||
10 | ||
11 | SYNOPSIS | |
12 | -------- | |
13 | [verse] | |
ce19b9ed | 14 | *lttng* ['linkgenoptions:(GENERAL OPTIONS)'] *start* ['SESSION'] |
30ec772c PP |
15 | |
16 | ||
17 | DESCRIPTION | |
18 | ----------- | |
19 | The `lttng start` command starts the various LTTng tracers for a | |
20 | given inactive tracing session. | |
21 | ||
22 | Starting the LTTng tracers has the effect that all enabled event rules | |
23 | within enabled channels can make their target event sources _emit_ trace | |
24 | events. Whether they are recorded to the local file system, sent over | |
25 | the network, or not recorded at all depends on the specific | |
26 | configuration of the tracing session in which tracing is started. See | |
7c1a4458 | 27 | man:lttng-create(1) for different session modes. |
30ec772c PP |
28 | |
29 | A tracing session with running tracers is said to be _active_. Active | |
30 | tracing sessions can return to the inactive state using the | |
7c1a4458 | 31 | man:lttng-stop(1) command. |
30ec772c PP |
32 | |
33 | If 'SESSION' is omitted, the LTTng tracers are started for the current | |
7c1a4458 | 34 | tracing session (see man:lttng-create(1) for more information |
30ec772c PP |
35 | about the current tracing session). Otherwise, they are started for the |
36 | existing tracing session named 'SESSION'. `lttng list` | |
7c1a4458 | 37 | outputs all the existing tracing sessions (see man:lttng-list(1)). |
30ec772c PP |
38 | |
39 | ||
40 | include::common-cmd-options-head.txt[] | |
41 | ||
42 | ||
43 | include::common-cmd-help-options.txt[] | |
44 | ||
45 | ||
46 | include::common-cmd-footer.txt[] | |
47 | ||
48 | ||
49 | SEE ALSO | |
50 | -------- | |
7c1a4458 PP |
51 | man:lttng-stop(1), |
52 | man:lttng(1) |