https://bugs.lttng.org/https://bugs.lttng.org/themes/lttng/favicon/a.ico?14249722912012-12-04T15:04:07ZLTTng bugs repositoryLTTng-tools - Bug #408: disable-event -u -a disables _all_ events (not just wildcards)https://bugs.lttng.org/issues/408?journal_id=9552012-12-04T15:04:07ZDavid Goulet
<ul></ul><p>Nope not suppose to happen.</p>
<p>It's working for me so maybe a weird version of UST or ... ?</p>
<p>I can confirm that ust* gets disabled:</p>
<p>DEBUG1: UST app disabling event ust* for all apps in channel channel0 for session id 0 [in ust_app_disable_event_glb() at ust-app.c:1887]<br />DEBUG2: Event UST ust* disabled in channel channel0 [in event_ust_disable_tracepoint() at event.c:560]</p> LTTng-tools - Bug #408: disable-event -u -a disables _all_ events (not just wildcards)https://bugs.lttng.org/issues/408?journal_id=10202012-12-20T16:43:42ZDavid Goulet
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Confirmed</i></li><li><strong>Assignee</strong> deleted (<del><i>David Goulet</i></del>)</li><li><strong>Priority</strong> changed from <i>Normal</i> to <i>Low</i></li><li><strong>Target version</strong> set to <i>2.2</i></li></ul><p>This is indeed a difference between enable and disable.</p>
<p>For 2.x, we can't really change the behavior of the options nor change it since we'll be facing an "API" breakage on the UI front. I'll flag this issue for 2.2 and see what we can do in the future about it.</p> LTTng-tools - Bug #408: disable-event -u -a disables _all_ events (not just wildcards)https://bugs.lttng.org/issues/408?journal_id=10232012-12-20T16:49:40ZYannick Brosseauyannick.brosseau@polymtl.ca
<ul></ul><p>As a user I would expect that the disable -u -a disable ALL events even the ones added with wildcard...</p> LTTng-tools - Bug #408: disable-event -u -a disables _all_ events (not just wildcards)https://bugs.lttng.org/issues/408?journal_id=10252012-12-20T16:53:32ZDavid Goulet
<ul></ul><p>It does yes.</p>
<p><a class="email" href="mailto:bugs@lttng.org">bugs@lttng.org</a>:</p>
<blockquote>
<p>Issue <a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: disable-event -u -a disables _all_ events (not just wildcards) (Resolved)" href="https://bugs.lttng.org/issues/408">#408</a> has been updated by Yannick Brosseau.</p>
<p>As a user I would expect that the disable <del>u -a disable ALL events even the ones added with wildcard...<br />---------------------------------------</del><br />Bug <a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: disable-event -u -a disables _all_ events (not just wildcards) (Resolved)" href="https://bugs.lttng.org/issues/408">#408</a>: disable-event -u -a disables <em>all</em> events (not just wildcards)<br /><a class="external" href="https://bugs.lttng.org/issues/408#change-1023">https://bugs.lttng.org/issues/408#change-1023</a></p>
<p>Author: Mathieu Desnoyers<br />Status: Confirmed<br />Priority: Low<br />Assignee: <br />Category: <br />Target version: 2.2</p>
<p>Wondering what should happen here:</p>
<p>lttng create<br />lttng enable-event -u 'ust*' --filter 'intfield==42'<br />lttng enable-event -u -a<br />lttng disable-event -u -a<br />lttng start</p>
<p>./hello<br />lttng stop; lttng view</p>
<p>Expected: 1 event with intfield == 42, result: no event at all.</p>
<p>However, if we use the '*' wildcard instead of -a, we get the expected result. I would have expected -a to behave in the same way as '*', but it's not the case for disable. Any reason for that ?</p>
<p>Thanks,</p>
<p>Mathieu</p>
</blockquote> LTTng-tools - Bug #408: disable-event -u -a disables _all_ events (not just wildcards)https://bugs.lttng.org/issues/408?journal_id=10272012-12-20T17:02:35ZYannick Brosseauyannick.brosseau@polymtl.ca
<ul></ul><p>Ok, reading the issue, I thought you wanted to -u -a to not disable the<br />event added with the -u "ust*"</p> LTTng-tools - Bug #408: disable-event -u -a disables _all_ events (not just wildcards)https://bugs.lttng.org/issues/408?journal_id=10292012-12-20T17:18:00ZDavid Goulet
<ul><li><strong>Status</strong> changed from <i>Confirmed</i> to <i>Resolved</i></li></ul><p>This has been documented in the man page.</p>
<p>Closing it.</p>