From 46adfb4b867899cd3f05171d0dbce70302022bcc Mon Sep 17 00:00:00 2001 From: Philippe Proulx Date: Mon, 19 Nov 2018 16:54:47 -0500 Subject: [PATCH] 2.10, 2.11: do not use `lttng stop`, then `lttng destroy` (implicit) Signed-off-by: Philippe Proulx --- 2.10/lttng-docs-2.10.txt | 32 +++++++++++++++++++++----------- 2.11/lttng-docs-2.11.txt | 32 +++++++++++++++++++++----------- 2 files changed, 42 insertions(+), 22 deletions(-) diff --git a/2.10/lttng-docs-2.10.txt b/2.10/lttng-docs-2.10.txt index 6d64ab8..1e3b904 100644 --- a/2.10/lttng-docs-2.10.txt +++ b/2.10/lttng-docs-2.10.txt @@ -868,22 +868,23 @@ tracepoints (this will generate a lot of data when tracing): . Do some operation on your system for a few seconds. For example, load a website, or list the files of a directory. -. <> and destroy the +. <> the current tracing session: + -- [role="term"] ---- -# lttng stop # 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. ++ +The man:lttng-destroy(1) command also runs the man:lttng-stop(1) command +implicitly (see <>). You need to stop tracing to make LTTng flush the remaining +trace data and make the trace readable. . For the sake of this example, make the recorded trace accessible to the non-root users: @@ -1116,22 +1117,23 @@ $ lttng start . Go back to the running `hello` application and press Enter. The program executes all `tracepoint()` instrumentation points and exits. -. <> and destroy the +. <> the current tracing session: + -- [role="term"] ---- -$ lttng stop $ 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. ++ +The man:lttng-destroy(1) command also runs the man:lttng-stop(1) command +implicitly (see <>). You need to stop tracing to make LTTng flush the remaining +trace data and make the trace readable. By default, LTTng saves the traces in +$LTTNG_HOME/lttng-traces/__name__-__date__-__time__+, @@ -5769,6 +5771,11 @@ $ lttng destroy ---- -- +The man:lttng-destroy(1) command also runs the man:lttng-stop(1) +command implicitly (see <>). You need to stop tracing to make LTTng flush the +remaining trace data and make the trace readable. + [[list-instrumentation-points]] === List the available instrumentation points @@ -6118,7 +6125,10 @@ 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. +trace data and make the trace readable. Note that the +man:lttng-destroy(1) command (see +<>) also runs the man:lttng-stop(1) command implicitly. [[enabling-disabling-channels]] diff --git a/2.11/lttng-docs-2.11.txt b/2.11/lttng-docs-2.11.txt index 54a72e4..5752c97 100644 --- a/2.11/lttng-docs-2.11.txt +++ b/2.11/lttng-docs-2.11.txt @@ -674,22 +674,23 @@ tracepoints (this will generate a lot of data when tracing): . Do some operation on your system for a few seconds. For example, load a website, or list the files of a directory. -. <> and destroy the +. <> the current tracing session: + -- [role="term"] ---- -# lttng stop # 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. ++ +The man:lttng-destroy(1) command also runs the man:lttng-stop(1) command +implicitly (see <>). You need to stop tracing to make LTTng flush the remaining +trace data and make the trace readable. . For the sake of this example, make the recorded trace accessible to the non-root users: @@ -922,22 +923,23 @@ $ lttng start . Go back to the running `hello` application and press Enter. The program executes all `tracepoint()` instrumentation points and exits. -. <> and destroy the +. <> the current tracing session: + -- [role="term"] ---- -$ lttng stop $ 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. ++ +The man:lttng-destroy(1) command also runs the man:lttng-stop(1) command +implicitly (see <>). You need to stop tracing to make LTTng flush the remaining +trace data and make the trace readable. By default, LTTng saves the traces in +$LTTNG_HOME/lttng-traces/__name__-__date__-__time__+, @@ -5557,6 +5559,11 @@ $ lttng destroy ---- -- +The man:lttng-destroy(1) command also runs the man:lttng-stop(1) +command implicitly (see <>). You need to stop tracing to make LTTng flush the +remaining trace data and make the trace readable. + [[list-instrumentation-points]] === List the available instrumentation points @@ -5935,7 +5942,10 @@ 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. +trace data and make the trace readable. Note that the +man:lttng-destroy(1) command (see +<>) also runs the man:lttng-stop(1) command implicitly. [[enabling-disabling-channels]] -- 2.34.1