.TH "LTTNG" "1" "May 13th, 2014" "" ""
.SH "NAME"
-lttng \(em LTTng 2.x tracer control command line tool
+lttng \- LTTng 2.x tracer control command line tool
.SH "SYNOPSIS"
.SH "OPTIONS"
.PP
-This program follow the usual GNU command line syntax with long options starting with
+This program follows the usual GNU command line syntax with long options starting with
two dashes. Below is a summary of the available options.
.PP
.BR "\-h, \-\-help"
Show summary of possible options and commands.
.TP
+.BR "\-V, \-\-version"
+Show version.
+.TP
.BR "\-v, \-\-verbose"
Increase verbosity.
Three levels of verbosity are available which are triggered by putting additional v to
when used with PRAMFS or other persistent memory filesystems to extract
trace data in the event of a crash requiring a reboot.
+See the \fBlttng-crash(1)\fP utility for more information on crash recovery.
+
.TP
.BR "\-U, \-\-set-url=URL"
Set URL for the consumer output destination. It is persistent for the
.PP
.PP
-\fBenable-event\fP NAME[,NAME2,...] [-k|-u] [OPTIONS]
+\fBenable-event\fP NAME[,NAME2,...] (\-k | \-u | \-j | \-l | \-p) [OPTIONS]
.RS
Enable tracing event
Specifying a filter is only allowed when enabling events within a session before
tracing is started. If the filter fails to link with the event
within the traced domain, the event will be discarded.
-Filtering is currently only implemented for the user-space tracer.
Expression examples:
.BR lttng-ust(3),
.BR lttng-sessiond(8),
.BR lttng-relayd(8),
+.BR lttng-crash(1),
.SH "BUGS"