[lttng-dev] Event redefinition/re-enablement
Ruslan Uvashev
ruslan.uvashev at gmail.com
Sun Mar 16 03:41:28 EDT 2014
Hi,
It seems that event once enabled for a channel cannot be reassigned to
another channel.
If events are immutable will Feature #445 (https://bugs.lttng.org/issues/445)
account such situation? Or do we need to update man saying that events
cannot be redefined?
Command output below.
Thank you!
Output:
$ sudo lttng create tst1
Session tst1 created.
Traces will be written in /home/rusty/lttng-traces/tst1-20140315-173020
$ sudo lttng enable-event writeback_nothread -k
Kernel event writeback_nothread created in channel channel0
$ sudo lttng enable-channel ch1 -k
Kernel channel ch1 enabled for session tst1
$ sudo lttng list tst1
Tracing session tst1: [inactive]
Trace path: /home/rusty/lttng-traces/tst1-20140315-173020
=== Domain: Kernel ===
Channels:
-------------
- ch1: [enabled]
Attributes:
overwrite mode: 0
subbufers size: 262144
number of subbufers: 4
switch timer interval: 0
read timer interval: 200000
output: splice()
Events:
None
- channel0: [enabled]
Attributes:
overwrite mode: 0
subbufers size: 262144
number of subbufers: 4
switch timer interval: 0
read timer interval: 200000
output: splice()
Events:
writeback_nothread (loglevel: TRACE_EMERG (0)) (type: tracepoint)
[enabled]
$ sudo lttng disable-event writeback_nothread -k -c channel0
Kernel event writeback_nothread disabled in channel channel0 for session
tst1
$ sudo lttng enable-event writeback_nothread -k -c ch1
Error: Event writeback_nothread: Enable kernel event failed (channel ch1,
session tst1)
Warning: Some command(s) went wrong
-------------------------------------
Best regards,
Ruslan Uvashev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lttng.org/pipermail/lttng-dev/attachments/20140316/f3133c83/attachment.html>
More information about the lttng-dev
mailing list