From 50a3b92a9ee3779d8daa8292067290bea8889346 Mon Sep 17 00:00:00 2001 From: David Goulet Date: Wed, 14 Nov 2012 12:40:32 -0500 Subject: [PATCH] Fix: add the notion of domain to lttng.1 man page Fixes #194 Signed-off-by: David Goulet --- doc/man/lttng.1 | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/doc/man/lttng.1 b/doc/man/lttng.1 index 468ed6940..5c94af4e1 100644 --- a/doc/man/lttng.1 +++ b/doc/man/lttng.1 @@ -23,11 +23,18 @@ be done by this tool or by the liblttng-ctl provided with the lttng-tools package. LTTng uses a session daemon (lttng-sessiond(8)), acting as a tracing registry, -which permits you to interact with multiple tracers (kernel and user-space) +which allows you to interact with multiple tracers (kernel and user-space) inside the same container, a tracing session. Traces can be gathered from the kernel and/or instrumented applications (lttng-ust(3)). Aggregating and reading those traces is done using the babeltrace(1) text viewer. +We introduce the notion of \fBtracing domains\fP which is essentially a type of +tracer (kernel or user space for now). In the future, we could see a third +tracer being for instance an hypervisor. For some commands, you'll need to +specify on which domain the command applies (-u or -k). For instance, enabling +a kernel event, you must specify the kernel domain to the command so we know +for which tracer this event is for. + In order to trace the kernel, the session daemon needs to be running as root. LTTng provides the use of a \fBtracing group\fP (default: tracing). Whomever is in that group can interact with the root session daemon and thus trace the -- 2.34.1