Deprecate lttng-cli.txt file

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

diff --git a/doc/quickstart.txt b/doc/quickstart.txt
index 5ba0cc54e247e7430cf849e8dc49d9e37cdc7f51..7078eecc97fb581621b58a250a448ac1f2724c59 100644 (file)
--- a/doc/quickstart.txt
+++ b/doc/quickstart.txt
@@ -18,7 +18,7 @@ installed. See http://lttng.org/lttng2.0 for more instructions for that part.
 For user-space tracing, you'll need an instrumented application, please see
 http://lttng.org/ust.
 
-lttng-tools provide a session daemon (ltt-sessiond) that acts as a tracing
+lttng-tools provide a session daemon (lttng-sessiond) that acts as a tracing
 registry. To trace any instrumented applications or the kernel, a registered
 tracing session is needed beforehand. To interact with the session daemon and a
 tracing session, you should use the lttng command line UI (lttng).
@@ -36,7 +36,7 @@ The next sections explain how to do tracing :)
 Kernel Tracing
 --------------
 
-You can start the session daemon by invoking the command "ltt-sessiond",
+You can start the session daemon by invoking the command "lttng-sessiond",
 or let the lttng command line tool do it for you. The session daemon
 loads the LTTng tracer modules for you if those modules can be found on
 your system. If they are not found, the kernel tracing feature will be
@@ -78,7 +78,7 @@ This is a new feature made possible by the new LTTng 2.0 kernel tracer. You can
 enable a dynamic probe and data will be output in the trace along side with
 your tracing data.
 
-# lttng enable-event aname -k --probe symbol+0xffff7260695
+# lttng enable-event aname -k --probe symbol+0x0
 
 or
 
@@ -149,7 +149,7 @@ human-readable text format. Please see
 http://www.efficios.com/babeltrace and git tree
 http://git.efficios.com/?p=babeltrace.git
 
-# babeltrace -n $HOME/lttng-traces/mysession-<date>-<time> | less
+# babeltrace $HOME/lttng-traces/mysession-<date>-<time> | less
 
 Voilà!