X-Git-Url: http://git.lttng.org./?a=blobdiff_plain;f=contents%2Funderstanding-lttng%2Fplumbing%2Flttng-sessiond.md;h=4469902f89f7363b3bd6ec2cd8f4c23faabf9a43;hb=b7189a67bfba753671c21dbaad05361b3a702563;hp=a1bb7f2ed8f64396285977932945221a3875937a;hpb=47bfcb757a0192864b56d12d775f65dc8b180aaf;p=lttng-docs.git diff --git a/contents/understanding-lttng/plumbing/lttng-sessiond.md b/contents/understanding-lttng/plumbing/lttng-sessiond.md index a1bb7f2..4469902 100644 --- a/contents/understanding-lttng/plumbing/lttng-sessiond.md +++ b/contents/understanding-lttng/plumbing/lttng-sessiond.md @@ -7,8 +7,8 @@ by its command name, `lttng-sessiond`. The session daemon is responsible for managing tracing sessions and what they logically contain (channel properties, enabled/disabled -events, etc.). By communicating locally with instrumented applications -(using LTTng-UST) and with the LTTng Linux kernel modules +events, and the rest). By communicating locally with instrumented +applications (using LTTng-UST) and with the LTTng Linux kernel modules (LTTng-modules), it oversees all tracing activities. One of the many things that `lttng-sessiond` does is to keep @@ -24,7 +24,7 @@ and user space tracers, the session daemon can send channel information so that they are initialized, enable/disable specific probes based on enabled/disabled events by the user, send event filters information to LTTng tracers so that filtering actually happens at the tracer site, -start/stop tracing a specific application or the Linux kernel, etc. +start/stop tracing a specific application or the Linux kernel, and more. The session daemon is not useful without some user controlling it, because it's only a sophisticated control interchange and thus @@ -44,7 +44,7 @@ Session daemons run on a per-user basis. Knowing this, multiple instances of `lttng-sessiond` may run simultaneously, each belonging to a different user and each operating independently of the others. Only `root`'s session daemon, however, may control LTTng kernel modules -(i.e. the kernel tracer). With that in mind, if a user has no root +(that is, the kernel tracer). With that in mind, if a user has no root access on the target system, he cannot trace the system's kernel, but should still be able to trace its own instrumented applications. @@ -78,5 +78,5 @@ pkill lttng-sessiond The default `SIGTERM` signal terminates it cleanly. Several other options are available and described in -lttng-sessiond's manpage -or by running `lttng-sessiond --help`. +lttng-sessiond's +man page or by running `lttng-sessiond --help`.