doc/man/manpage.xsl: do not indent the title of an admonition block
[lttng-tools.git] / doc / man / lttng-destroy.1.txt
CommitLineData
7bf169bd 1lttng-destroy(1)
4605890e 2================
484b2a0c 3:revdate: 12 April 2021
7bf169bd
PP
4
5
6NAME
7----
484b2a0c 8lttng-destroy - Destroy LTTng tracing sessions
7bf169bd
PP
9
10
11SYNOPSIS
12--------
13[verse]
d0d2c3e4 14*lttng* ['linkgenoptions:(GENERAL OPTIONS)'] *destroy* [option:--no-wait] [option:--all | 'SESSION']
7bf169bd
PP
15
16
17DESCRIPTION
18-----------
484b2a0c
PP
19The `lttng destroy` command destroys one or more tracing sessions
20previously created with the man:lttng-create(1) command.
7bf169bd 21
484b2a0c
PP
22``Destroying'' a tracing session means freeing the resources acquired by
23the LTTng daemons and tracers for it, also making sure to flush all the
24recorded trace data to either the local file system or the connected
25LTTng relay daemon (see man:lttng-relayd(8)), depending on the tracing
26session mode.
7bf169bd 27
484b2a0c 28Use the `destroy` command to destroy:
7bf169bd 29
484b2a0c
PP
30With the 'SESSION' argument::
31 The tracing session named 'SESSION'.
7bf169bd 32
484b2a0c
PP
33With the option:--all option::
34 *All* the tracing sessions of your Unix user,
35 as listed in the output of `lttng list` (see man:lttng-list(1)).
7bf169bd 36
484b2a0c
PP
37Otherwise::
38 The current tracing session (see man:lttng-create(1) and
39 man:lttng-set-session(1) to learn more about the current tracing
40 session).
41+
42In that case, the current tracing session becomes nonexistent.
7bf169bd 43
484b2a0c
PP
44The `destroy` command stops any tracing activity within the selected
45tracing session(s). By default, the command runs the implicit
46man:lttng-stop(1) command to ensure that the trace data of the tracing
47session(s) is valid before it exits. Make the command exit immediately
48with the option:--no-wait option. In this case, however, the traces(s)
49might not be valid when the command exits, and there's no way to know
50when it/they becomes valid.
51
52If, for a tracing session{nbsp}__TS__ to destroy with the `destroy`
53command, the following statements are true:
54
55* You don't use the option:--no-wait option.
56
57* LTTng archived the current trace chunk (see man:lttng-rotate(1) and
58 man:lttng-enable-rotation(1)) of{nbsp}__TS__ at least once during its
59 lifetime.
60
61Then all the subdirectories of the output directory of{nbsp}__TS__
62(local or remote) are considered trace chunk archives once the `destroy`
63command exits. In other words, it's safe to read them, modify them, move
64them, or remove then.
980bb5fd 65
7bf169bd
PP
66
67include::common-cmd-options-head.txt[]
68
69
70option:-a, option:--all::
484b2a0c
PP
71 Destroy all the tracing sessions of your Unix user, as listed in the
72 output of man:lttng-list(1).
7bf169bd 73
d0d2c3e4 74option:-n, option:--no-wait::
484b2a0c
PP
75 Do :not: ensure that the trace data of the tracing session(s) to
76 destroy is valid before exiting.
d0d2c3e4 77
7bf169bd
PP
78
79include::common-cmd-help-options.txt[]
80
81
82include::common-cmd-footer.txt[]
83
84
85SEE ALSO
86--------
484b2a0c 87man:lttng(1),
7c1a4458 88man:lttng-create(1),
484b2a0c
PP
89man:lttng-list(1),
90man:lttng-set-session(1)
This page took 0.033972 seconds and 4 git commands to generate.