The lttng-list command uses the following domain headers
when printing domain listings:
- `Kernel`
- `UST global`
- `JUL (Java Util Logging)`
- `LOG4j (Logging for Java)`
- `Python (logging)`
Those don't match the official project names and/or names
used in the LTTng online documentation.
They are replaced by:
- `Linux kernel`
- `User space`
- `java.util.logging (JUL)`
- `log4j`
- `Python logging`
Signed-off-by: Jérémie Galarneau <jeremie.galarneau@efficios.com>
Change-Id: I549b309eebf0d00dfaacbed00e263f4e5e3d718b
for (i = 0; i < nb_domain; i++) {
switch (domains[i].type) {
case LTTNG_DOMAIN_KERNEL:
for (i = 0; i < nb_domain; i++) {
switch (domains[i].type) {
case LTTNG_DOMAIN_KERNEL:
- MSG("=== Domain: Kernel ===\n");
+ MSG("=== Domain: Linux kernel ===\n");
break;
case LTTNG_DOMAIN_UST:
break;
case LTTNG_DOMAIN_UST:
- MSG("=== Domain: UST global ===\n");
+ MSG("=== Domain: User space ===\n");
MSG("Buffering scheme: %s\n",
domains[i].buf_type ==
LTTNG_BUFFER_PER_PID ? "per-process" : "per-user");
break;
case LTTNG_DOMAIN_JUL:
MSG("Buffering scheme: %s\n",
domains[i].buf_type ==
LTTNG_BUFFER_PER_PID ? "per-process" : "per-user");
break;
case LTTNG_DOMAIN_JUL:
- MSG("=== Domain: JUL (Java Util Logging) ===\n");
+ MSG("=== Domain: java.util.logging (JUL) ===\n");
break;
case LTTNG_DOMAIN_LOG4J:
break;
case LTTNG_DOMAIN_LOG4J:
- MSG("=== Domain: LOG4j (Logging for Java) ===\n");
+ MSG("=== Domain: log4j ===\n");
break;
case LTTNG_DOMAIN_PYTHON:
break;
case LTTNG_DOMAIN_PYTHON:
- MSG("=== Domain: Python (logging) ===\n");
+ MSG("=== Domain: Python logging ===\n");
break;
default:
MSG("=== Domain: Unimplemented ===\n");
break;
default:
MSG("=== Domain: Unimplemented ===\n");