From: Philippe Proulx <eeppeliteloop@gmail.com>
Date: Fri, 4 Sep 2015 21:47:51 +0000 (-0400)
Subject: tracef: minor fixes
X-Git-Url: https://git.lttng.org./?a=commitdiff_plain;h=222d59752bd3490051dfb4103be200dbc0265b84;p=lttng-docs.git

tracef: minor fixes

Signed-off-by: Philippe Proulx <eeppeliteloop@gmail.com>
---

diff --git a/contents/using-lttng/instrumenting/c-application/tracef.md b/contents/using-lttng/instrumenting/c-application/tracef.md
index 8918e76..1ec93c2 100644
--- a/contents/using-lttng/instrumenting/c-application/tracef.md
+++ b/contents/using-lttng/instrumenting/c-application/tracef.md
@@ -12,7 +12,7 @@ super simple, albeit with notable disadvantages compared to custom,
 full-fledged tracepoint providers:
 
   * All generated events have the same provider/event names, respectively
-    `lttng-ust-tracef` and `event`.
+    `lttng_ust_tracef` and `event`.
   * There's no static type checking.
   * The only event field you actually get, named `msg`, is a string
     potentially containing the values you passed to the function
@@ -59,4 +59,9 @@ Execute the application as usual:
 </pre>
 
 Voilà! Use the `lttng` command line tool to
-[control tracing](#doc-controlling-tracing).
+[control tracing](#doc-controlling-tracing). You can enable `tracef()`
+events like this:
+
+<pre class="term">
+lttng enable-event --userspace 'lttng_ust_tracef:*'
+</pre>