lttng: Add remove-trigger command

[lttng-tools.git] / doc / man / lttng-start.1.txt

diff --git a/doc/man/lttng-start.1.txt b/doc/man/lttng-start.1.txt
index 2c9405bacc82336a8e391398d0ba2624eac7ad01..a6868f16077c778e38d0d816df98b82b74a6a33e 100644 (file)
--- a/doc/man/lttng-start.1.txt
+++ b/doc/man/lttng-start.1.txt
@@ -1,5 +1,6 @@
 lttng-start(1)
 ==============
+:revdate: 7 April 2016
 
 
 NAME
@@ -23,17 +24,17 @@ within enabled channels can make their target event sources _emit_ trace
 events. Whether they are recorded to the local file system, sent over
 the network, or not recorded at all depends on the specific
 configuration of the tracing session in which tracing is started. See
-linklttng:lttng-create(1) for different session modes.
+man:lttng-create(1) for different session modes.
 
 A tracing session with running tracers is said to be _active_. Active
 tracing sessions can return to the inactive state using the
-linklttng:lttng-stop(1) command.
+man:lttng-stop(1) command.
 
 If 'SESSION' is omitted, the LTTng tracers are started for the current
-tracing session (see linklttng:lttng-create(1) for more information
+tracing session (see man:lttng-create(1) for more information
 about the current tracing session). Otherwise, they are started for the
 existing tracing session named 'SESSION'. `lttng list`
-outputs all the existing tracing sessions (see linklttng:lttng-list(1)).
+outputs all the existing tracing sessions (see man:lttng-list(1)).
 
 
 include::common-cmd-options-head.txt[]
@@ -47,5 +48,5 @@ include::common-cmd-footer.txt[]
 
 SEE ALSO
 --------
-linklttng:lttng-stop(1),
-linklttng:lttng(1)
+man:lttng-stop(1),
+man:lttng(1)