Fix: action executor: double work list unlock on error

[lttng-tools.git] / doc / quickstart.txt

diff --git a/doc/quickstart.txt b/doc/quickstart.txt
index f7ec99d373d166743fb39bdb6591c48dafd32c31..9bcb8460469505f8834b86cce940111ca8bd0aa2 100644 (file)
--- a/doc/quickstart.txt
+++ b/doc/quickstart.txt
@@ -13,11 +13,11 @@ This is a quick start guide for the complete LTTng tool chain. This is divided
 in three sections respectively kernel tracing, user-space tracing and reading a
 trace.
 
-See the README file for installation procedure or use the various Linux
+See the README.adoc file for installation procedure or use the various Linux
 distribution packages.
 
 In order to trace the kernel, you'll need the lttng-modules 2.0 compiled and
-installed. See http://lttng.org/lttng2.0 for more instructions for that part.
+installed. See https://lttng.org/lttng2.0 for more instructions for that part.
 For user-space tracing, you'll need an instrumented application with lttng-ust
 2.0.
 
@@ -161,7 +161,7 @@ applications. However, if you run the session daemon under non-root user
 rights, only applications of that user will be traced.
 
 So, after instrumenting you applications with LTTng-ust 2.0
-(http://lttng.org/lttng2.0), upon startup, it will automatically register to
+(https://lttng.org/lttng2.0), upon startup, it will automatically register to
 the session daemon. If there is none running, it will simply wait on a seperate
 thread for a session daemon to appear and then register.
 
@@ -206,8 +206,8 @@ $ lttng add-context -u -e ust_tests_hello:tptest -t pid -t nice -t tid
 
 $ lttng start
 
-Tracing is in progress at this point and traces will be written in
-$HOME/lttng-traces/mysession-<date>-<time>/ust/<procname>-<pid>-<date>-<time>
+Tracing is in progress at this point and traces will be written in the session
+directory.
 
 NOTE: It will start tracing for *all* domain(s).