projects
/
lttng-tools.git
/ blobdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
|
commitdiff
|
tree
raw
|
inline
| side by side
Launch the application notification thread using lttng_thread
[lttng-tools.git]
/
doc
/
quickstart.txt
diff --git
a/doc/quickstart.txt
b/doc/quickstart.txt
index 50e155e85ec584adf5c19af2a4bbc2e32caed6df..0e9751b599185e6719758b82436cee821c1448b4 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.
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
.md
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
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 http
s
://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.
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
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
+(http
s
://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.
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.
This page took
0.024296 seconds
and
4
git commands to generate.