Project

General

Profile

Actions
Copy link

Bug #913

closed

Issuing both --loglevel and --loglevel-only for the same event and same level does not work

Added by Anonymous over 9 years ago. Updated about 9 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Philippe Proulx
Target version:
LTTng - 2.7
Start date:
08/29/2015
Due date:
% Done:

0%

Estimated time:

Description

If one enables an event for a given loglevel range (--loglevel), a subsequent enable for a specific loglevel (--loglevel-only) will not throw any error, but will have no effect.

For example:

lttng create
lttng enable-event -j myevent --loglevel warning
lttng enable-event -j myevent --loglevel-only warning

lttng list will still only show:

Events (Logger name):
---------------------
    - myevent [enabled] (loglevel <= JUL_WARNING)

It seems like a bug, as those are two different "event rules" and could be enabled side-by-side.

Note that if the two log levels are different (even if the conditions are "overlapping"), then it works correctly:

lttng create
lttng enable-event -j myevent --loglevel warning
lttng enable-event -j myevent --loglevel-only severe

lttng list then shows

Events (Logger name):
---------------------
    - myevent [enabled] (loglevel == JUL_SEVERE)
    - myevent [enabled] (loglevel <= JUL_WARNING)
Actions
Copy link

Also available in: Atom PDF