aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDr. David Alan Gilbert <dgilbert@redhat.com>2014-10-07 15:12:41 +0100
committerStefan Hajnoczi <stefanha@redhat.com>2014-11-18 14:05:54 +0000
commitb73e8bd414b70f7ee63474cbddce0fb809e56a5d (patch)
tree88474e5b17819cb890c40e87401a5d15a198ff79
parent1aba4be97eb01b650d146c7f01dc961d55da62ab (diff)
Tracing docs fix configure option and description
Fix the example trace configure option. Update the text to say that multiple backends are allowed and what happens when multiple backends are enabled. Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com> Message-id: 1412691161-31785-1-git-send-email-dgilbert@redhat.com Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
-rw-r--r--docs/tracing.txt6
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/tracing.txt b/docs/tracing.txt
index 7d38926394..7117c5e7d6 100644
--- a/docs/tracing.txt
+++ b/docs/tracing.txt
@@ -139,12 +139,12 @@ events are not tightly coupled to a specific trace backend, such as LTTng or
SystemTap. Support for trace backends can be added by extending the "tracetool"
script.
-The trace backend is chosen at configure time and only one trace backend can
-be built into the binary:
+The trace backends are chosen at configure time:
- ./configure --trace-backends=simple
+ ./configure --enable-trace-backends=simple
For a list of supported trace backends, try ./configure --help or see below.
+If multiple backends are enabled, the trace is sent to them all.
The following subsections describe the supported trace backends.