Actions
Bug #571
closedlttng-tools 2.2.0-rc2: kernel enable-channel for a suspended trace fails arbitrarily
Start date:
06/25/2013
Due date:
% Done:
100%
Estimated time:
Description
$ sudo -H lttng create sss $ sudo -H lttng enable-channel k0 -k Kernel channel k0 enabled for session sss $ sudo -H lttng enable-channel k1 -k --subbuf-size 4096 Kernel channel k1 enabled for session sss $ sudo -H lttng start Tracing started for session sss $ sudo -H lttng stop Waiting for data availability Tracing stopped for session sss $ sudo -H lttng enable-channel k2 -k --subbuf-size 4096 PERROR [20531/20631]: ioctl kernel create channel: Invalid argument (in kernel_create_channel() at kernel.c:144) Error: Channel k2: Kernel create channel failed (session sss) Warning: Some command(s) went wrong $ sudo -H lttng enable-channel k2 -k PERROR [20531/20631]: ioctl kernel create channel: Invalid argument (in kernel_create_channel() at kernel.c:144) Error: Channel k2: Kernel create channel failed (session sss) Warning: Some command(s) went wrong
This inability to enable new channels (for a suspended trace) seems to affect only the kernel domain (in the user-space domain, new channels may be enabled at any time, even while the trace is running). If this is a feature, it ought to be mentioned in the man pages.
Updated by David Goulet over 11 years ago
- Status changed from New to Confirmed
- Assignee set to David Goulet
- Target version set to 2.2
It's a limitation right now yes only for the lttng-modules.
I'll document that in the man page before any release.
Updated by David Goulet over 11 years ago
- Status changed from Confirmed to Resolved
- % Done changed from 0 to 100
Applied in changeset bd337b98fea4ce3f2073bf83394a3e6e3dd9cf71.
Actions