Project

General

Profile

Actions

Bug #802

closed

lttng client mentions "channel0" when creating a JUL channel

Added by Jérémie Galarneau almost 10 years ago. Updated almost 10 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Target version:
Start date:
05/30/2014
Due date:
% Done:

100%

Estimated time:

Description

Note how the enable-event command will create a channel named channel0 while the listing then shows a channel named lttng_jul_channel.

$ lttng create p1
Spawning a session daemon
Session p1 created.
Traces will be written in /home/jgalar/lttng-traces/p1-20140530-122643
$ lttng enable-event -j 'root.l'
JUL event root.l created in channel channel0
$ lttng list p1
Tracing session p1: [inactive]
    Trace path: /home/jgalar/lttng-traces/p1-20140530-122643
    Live timer interval (usec): 0

=== Domain: UST global ===

Buffer type: per UID

Channels:
-------------
- lttng_jul_channel: [enabled]

    Attributes:
      overwrite mode: 0
      subbufers size: 131072
      number of subbufers: 4
      switch timer interval: 0
      read timer interval: 0
      trace file count: 0
      trace file size (bytes): 0
      output: mmap()

    Events:
      lttng_jul:user* (type: tracepoint) [enabled] [with filter]

=== Domain: JUL (Java Util Logging) ===

Events (Logger name):
---------------------
    - root.l [enabled] (loglevel: JUL_ALL)
Actions #1

Updated by David Goulet almost 10 years ago

  • Status changed from New to Confirmed
  • Target version changed from 2.4 to 2.5

This is going into 2.5 because we can't change the printed message layout in stable release.

Fix is coming up in a jiffy.

Actions #2

Updated by David Goulet almost 10 years ago

  • Target version changed from 2.5 to 2.6

My mistake, 2.6 is the right version.

Actions #3

Updated by David Goulet almost 10 years ago

  • Status changed from Confirmed to Resolved
  • % Done changed from 0 to 100

Applied in changeset tools|commit:49ceaa707d6fd92526e6afb4beeca7bb77409fe2.

Actions

Also available in: Atom PDF