doc/man: refer to Babeltrace 2 instead of Babeltrace 1

Signed-off-by: Philippe Proulx <eeppeliteloop@gmail.com>
Change-Id: Icafd69f28304b14e49e8cf8e21d2c6ebe3e319b6
Signed-off-by: Jérémie Galarneau <jeremie.galarneau@efficios.com>

diff --git a/doc/man/lttng-crash.1.txt b/doc/man/lttng-crash.1.txt
index 25483847d13b5886c4225540170f945ccda2af07..f67a881353a7cf80e278214d7579d33a7274c1d4 100644 (file)
--- a/doc/man/lttng-crash.1.txt
+++ b/doc/man/lttng-crash.1.txt
@@ -1,6 +1,6 @@
 lttng-crash(1)
 ==============
-:revdate: 5 June 2018
+:revdate: 2 April 2020
 
 
 NAME
@@ -46,7 +46,8 @@ option:-e 'VIEWER', option:--viewer='VIEWER'::
     command arguments as well. The trace directory paths are passed to
     the 'VIEWER' command as its last arguments.
 +
-Default: `babeltrace`.
+Without this option, `lttng crash` uses man:babeltrace2(1) if it's
+available. Otherwise, it tries to use man:babeltrace(1).
 
 
 Program information
@@ -79,4 +80,4 @@ man:lttng(1),
 man:lttng-sessiond(8),
 man:lttng-relayd(8),
 man:lttng-ust(3),
-man:babeltrace(1)
+man:babeltrace2(1)

diff --git a/doc/man/lttng-relayd.8.txt b/doc/man/lttng-relayd.8.txt
index e70242d46170ff779487d800fd010e14e1ca07bf..f5a5bcd1067e9593bc4c007dc35a4522f0de268b 100644 (file)
--- a/doc/man/lttng-relayd.8.txt
+++ b/doc/man/lttng-relayd.8.txt
@@ -309,4 +309,4 @@ man:lttng(1),
 man:lttng-sessiond(8),
 man:lttng-crash(1),
 man:lttng-ust(3),
-man:babeltrace(1)
+man:babeltrace2(1)

diff --git a/doc/man/lttng-sessiond.8.txt b/doc/man/lttng-sessiond.8.txt
index 73a9717c591c86ae0511796b5cb301ad912ae0e7..e84c70b92d3f3b66b899b326b7689dd90178f1d4 100644 (file)
--- a/doc/man/lttng-sessiond.8.txt
+++ b/doc/man/lttng-sessiond.8.txt
@@ -42,7 +42,7 @@ to interact with multiple tracers (kernel and user space) within the
 same container, a _tracing session_. Traces can be gathered from the
 Linux kernel and/or from instrumented applications (see
 man:lttng-ust(3)). You can aggregate and read the events of LTTng
-traces using man:babeltrace(1).
+traces using man:babeltrace2(1).
 
 To trace the Linux kernel, the session daemon needs to be running as
 `root`. LTTng uses a _tracing group_ to allow specific users to interact
@@ -347,4 +347,4 @@ man:lttng(1),
 man:lttng-relayd(8),
 man:lttng-crash(1),
 man:lttng-ust(3),
-man:babeltrace(1)
+man:babeltrace2(1)

diff --git a/doc/man/lttng.1.txt b/doc/man/lttng.1.txt
index 4e02c765b20e1bdafc1747f0800b7c137837867b..8465ceeb4a2c477c52a952507f61aedd5d764ecb 100644 (file)
--- a/doc/man/lttng.1.txt
+++ b/doc/man/lttng.1.txt
@@ -56,7 +56,7 @@ interact with multiple tracers (kernel and user space) within the same
 container, a _tracing session_. Traces can be gathered from the Linux
 kernel and/or from instrumented applications (see
 man:lttng-ust(3)). You can aggregate and read the events of LTTng
-traces using man:babeltrace(1).
+traces using man:babeltrace2(1).
 
 To trace the Linux kernel, the session daemon needs to be running as
 `root`. LTTng uses a _tracing group_ to allow specific users to interact
@@ -252,4 +252,4 @@ man:lttng-sessiond(8),
 man:lttng-relayd(8),
 man:lttng-crash(1),
 man:lttng-ust(3),
-man:babeltrace(1)
+man:babeltrace2(1)