X-Git-Url: https://git.lttng.org/?a=blobdiff_plain;f=doc%2Fman%2Flttng-enable-channel.1.txt;h=b9c6d1696afd0c44042c70d0a457b3da70e5b5f7;hb=484b2a0cbefcf0c7072622a5a411ea5ed849da28;hp=787666ad5d1969d3f23598f1015c631443a8a99e;hpb=7197e9ec670114d94064a1b1658a9a2ca3b348a9;p=lttng-tools.git

diff --git a/doc/man/lttng-enable-channel.1.txt b/doc/man/lttng-enable-channel.1.txt
index 787666ad5..b9c6d1696 100644
--- a/doc/man/lttng-enable-channel.1.txt
+++ b/doc/man/lttng-enable-channel.1.txt
@@ -1,5 +1,6 @@
 lttng-enable-channel(1)
 =======================
+:revdate: 9 November 2018
 
 
 NAME
@@ -43,8 +44,8 @@ DESCRIPTION
 The `lttng enable-channel` command can create a new channel, or enable
 one or more existing and disabled ones.
 
-A channel is the owner of sub-buffers holding recorded events. Event,
-rules, when created using man:lttng-enable-event(1), are always
+A channel is the owner of sub-buffers holding recorded events. Recording
+event rules, when created using man:lttng-enable-event(1), are always
 assigned to a channel. When creating a new channel, many parameters
 related to those sub-buffers can be fine-tuned. They are described in
 the subsections below.
@@ -244,6 +245,14 @@ Here, for each stream, the maximum size of each trace file is
 no space left in the last file, _trace file rotation_ happens: the first
 file is cleared and new sub-buffers containing events are written there.
 
+LTTng does not guarantee that you can view the trace of an active
+tracing session before you run the man:lttng-stop(1) command, even
+with multiple trace files, because LTTng could overwrite them at any
+moment, or some of them could be incomplete. You can archive a
+tracing session's current trace chunk while the tracing session is
+active to obtain an unmanaged and self-contained LTTng trace: see
+the man:lttng-rotate(1) and man:lttng-enable-rotation(1) commands.
+
 
 include::common-cmd-options-head.txt[]