2.10, 2.11: `lttng stop` makes the trace readable

[lttng-docs.git] / 2.10 / lttng-docs-2.10.txt

diff --git a/2.10/lttng-docs-2.10.txt b/2.10/lttng-docs-2.10.txt
index 723be3474a78a5655a58b62428cf1a7655848c7f..6d64ab86f41dc2ef8d16f4748b223fe7999c232b 100644 (file)
--- a/2.10/lttng-docs-2.10.txt
+++ b/2.10/lttng-docs-2.10.txt
@@ -1,7 +1,7 @@
 The LTTng Documentation
 =======================
 Philippe Proulx <pproulx@efficios.com>
-v2.10, 12 November 2018
+v2.10, 19 November 2018
 
 
 include::../common/copyright.txt[]
@@ -879,6 +879,9 @@ tracepoints (this will generate a lot of data when tracing):
 ----
 --
 +
+You need to stop tracing to make LTTng flush the remaining trace data
+and make the trace readable.
++
 The man:lttng-destroy(1) command does not destroy the trace data; it
 only destroys the state of the tracing session.
 
@@ -1124,6 +1127,9 @@ $ lttng destroy
 ----
 --
 +
+You need to stop tracing to make LTTng flush the remaining trace data
+and make the trace readable.
++
 The man:lttng-destroy(1) command does not destroy the trace data; it
 only destroys the state of the tracing session.
 
@@ -6111,6 +6117,9 @@ records>> or lost sub-buffers since the last time you ran
 man:lttng-start(1), warnings are printed when you run the
 man:lttng-stop(1) command.
 
+IMPORTANT: You need to stop tracing to make LTTng flush the remaining
+trace data and make the trace readable.
+
 
 [[enabling-disabling-channels]]
 === Create a channel