events are contained in a specific channel, itself contained in a
specific tracing session. A channel is a group of events with
tunable parameters (event loss mode, sub-buffer size, number of
-sub-buffers, trace file sizes and count, etc.). A given channel may
-only be responsible for enabled events belonging to one domain: either
-kernel or user space.
+sub-buffers, trace file sizes and count, to name a few). A given channel
+may only be responsible for enabled events belonging to one domain:
+either kernel or user space.
If you only used the `create`, `enable-event` and `start`/`stop`
commands of the `lttng` tool so far, one or two channels were
lttng enable-channel --kernel my-channel
</pre>
-This will create a kernel domain channel named `my-channel` with
+This creates a kernel domain channel named `my-channel` with
default parameters in the current tracing session.
<div class="tip">
<p>
<span class="t">Note:</span>Because of a current limitation, all
channels must be <em>created</em> prior to beginning tracing in a
- given tracing session, i.e. before the first time you do
+ given tracing session, that is before the first time you do
<code>lttng start</code>.
</p>
<p>
--tracefile-size 1048576 1mib-channel
</pre>
-This will create a user space domain channel named `1mib-channel` in
+This creates a user space domain channel named `1mib-channel` in
the tracing session named `other-session` that loses new events by
overwriting previously recorded events (instead of the default mode of
discarding newer ones) and saves trace files with a maximum size of
lttng enable-event --userspace --channel other-channel app:tp
</pre>
-If both channels are enabled, the occurring `app:tp` event will
-generate two recorded events, one for each channel.
+If both channels are enabled, the occurring `app:tp` event
+generates two recorded events, one for each channel.
Disabling a channel is done with the `disable-event` command: