event-rule: introduce event rule syscall

[lttng-tools.git] / doc / man / lttng-stop.1.txt

diff --git a/doc/man/lttng-stop.1.txt b/doc/man/lttng-stop.1.txt
index e2997e64aec3c82398090f969299ac3f1a8a384c..55afcd3483345ffbc27c9f85b75812305f1e8929 100644 (file)
--- a/doc/man/lttng-stop.1.txt
+++ b/doc/man/lttng-stop.1.txt
@@ -1,5 +1,6 @@
 lttng-stop(1)
 =============
 lttng-stop(1)
 =============

+:revdate: 18 January 2018

 
 
 NAME
 
 
 NAME


@@ -38,13 +39,22 @@ option:--no-wait option, the command finishes immediately, hence a local
 trace might not be valid when the command is done. In this case, there
 is no way to know when the trace becomes valid.
 
 trace might not be valid when the command is done. In this case, there
 is no way to know when the trace becomes valid.
 

+If at least one rotation occurred during the chosen tracing session's
+lifetime (see man:lttng-rotate(1) and man:lttng-enable-rotation(1)), the
+`lttng stop` command renames the current trace chunk subdirectory and
+prints the renamed path. Although it is safe to read the content of this
+renamed subdirectory while the tracing session remains inactive (until
+the next man:lttng-start(1)), it is :not: a trace chunk archive: you
+need to destroy the tracing session with man:lttng-destroy(1) or make
+a rotation with man:lttng-rotate(1) to archive it.
+

 
 include::common-cmd-options-head.txt[]
 
 
 option:-n, option:--no-wait::
 
 include::common-cmd-options-head.txt[]
 
 
 option:-n, option:--no-wait::

-       Do not ensure that the chosen tracing session's trace data is valid
-       before returning to the prompt.
+    Do not ensure that the chosen tracing session's trace data is valid
+    before returning to the prompt.

 
 
 include::common-cmd-help-options.txt[]
 
 
 include::common-cmd-help-options.txt[]