Fix lttng UI: fix arg parsing, round size to next power of two
[lttng-tools.git] / doc / man / lttng.1
1 .TH "LTTNG" "1" "December 3rd, 2012" "" ""
2
3 .SH "NAME"
4 lttng \(em LTTng 2.1.x tracer control command line tool
5
6 .SH "SYNOPSIS"
7
8 .PP
9 .nf
10 lttng [OPTIONS] <COMMAND>
11 .fi
12 .SH "DESCRIPTION"
13
14 .PP
15 The LTTng project aims at providing highly efficient tracing tools for Linux.
16 It's tracers help tracking down performance issues and debugging problems
17 involving multiple concurrent processes and threads. Tracing across multiple
18 systems is also possible.
19
20 The \fBlttng\fP command line tool from the lttng-tools package is used to control
21 both kernel and user-space tracing. Every interactions with the tracer should
22 be done by this tool or by the liblttng-ctl provided with the lttng-tools
23 package.
24
25 LTTng uses a session daemon (lttng-sessiond(8)), acting as a tracing registry,
26 which allows you to interact with multiple tracers (kernel and user-space)
27 inside the same container, a tracing session. Traces can be gathered from the
28 kernel and/or instrumented applications (lttng-ust(3)). Aggregating and reading
29 those traces is done using the babeltrace(1) text viewer.
30
31 We introduce the notion of \fBtracing domains\fP which is essentially a type of
32 tracer (kernel or user space for now). In the future, we could see a third
33 tracer being for instance an hypervisor. For some commands, you'll need to
34 specify on which domain the command applies (-u or -k). For instance, enabling
35 a kernel event, you must specify the kernel domain to the command so we know
36 for which tracer this event is for.
37
38 In order to trace the kernel, the session daemon needs to be running as root.
39 LTTng provides the use of a \fBtracing group\fP (default: tracing). Whomever is
40 in that group can interact with the root session daemon and thus trace the
41 kernel. Session daemons can co-exist meaning that you can have a session daemon
42 running as Alice that can be used to trace her applications along side with a
43 root daemon or even a Bob daemon. We highly recommend to start the session
44 daemon at boot time for stable and long term tracing.
45
46 Every user-space applications instrumented with lttng-ust(3), will
47 automatically register to the session daemon. This feature gives you the
48 ability to list available traceable applications and tracepoints on a per user
49 basis. (See \fBlist\fP command).
50 .SH "OPTIONS"
51
52 .PP
53 This program follow the usual GNU command line syntax with long options starting with
54 two dashes. Below is a summary of the available options.
55 .PP
56
57 .TP
58 .BR "\-h, \-\-help"
59 Show summary of possible options and commands.
60 .TP
61 .BR "\-v, \-\-verbose"
62 Increase verbosity.
63 Three levels of verbosity are available which are triggered by putting additional v to
64 the option (\-vv or \-vvv)
65 .TP
66 .BR "\-q, \-\-quiet"
67 Suppress all messages (even errors).
68 .TP
69 .BR "\-g, \-\-group NAME"
70 Set unix tracing group name. (default: tracing)
71 .TP
72 .BR "\-n, \-\-no-sessiond"
73 Don't automatically spawn a session daemon.
74 .TP
75 .BR "\-\-sessiond\-path PATH"
76 Set session daemon full binary path.
77 .TP
78 .BR "\-\-list\-options"
79 Simple listing of lttng options.
80 .TP
81 .BR "\-\-list\-commands"
82 Simple listing of lttng commands.
83 .SH "COMMANDS"
84
85 .TP
86 \fBadd-context\fP
87 .nf
88 Add context to event(s) and/or channel(s).
89
90 A context is basically extra information appended to a channel. For instance,
91 you could ask the tracer to add the PID information for all events in a
92 channel. You can also add performance monitoring unit counters (perf PMU) using
93 the perf kernel API).
94
95 For example, this command will add the context information 'prio' and two perf
96 counters (hardware branch misses and cache misses), to all events in the trace
97 data output:
98
99 # lttng add-context \-k \-t prio \-t perf:branch-misses \-t perf:cache-misses
100
101 Please take a look at the help (\-h/\-\-help) for a detailed list of available
102 contexts.
103
104 If no channel is given (\-c), the context is added to all channels. Otherwise
105 the context will be added only to the given channel (\-c).
106
107 If \fB\-s, \-\-session\fP is omitted, the session name is taken from the .lttngrc
108 file.
109 .fi
110
111 .B OPTIONS:
112
113 .nf
114 \-h, \-\-help
115 Show summary of possible options and commands.
116 \-s, \-\-session NAME
117 Apply on session name.
118 \-c, \-\-channel NAME
119 Apply on channel name.
120 \-k, \-\-kernel
121 Apply for the kernel tracer
122 \-u, \-\-userspace
123 Apply for the user-space tracer
124 \-t, \-\-type TYPE
125 Context type. You can repeat this option on the command line. Please
126 use "lttng add-context \-h" to list all available types.
127 .fi
128
129 .IP
130
131 .IP "\fBcalibrate\fP"
132 .nf
133 Quantify LTTng overhead
134
135 The LTTng calibrate command can be used to find out the combined average
136 overhead of the LTTng tracer and the instrumentation mechanisms used. This
137 overhead can be calibrated in terms of time or using any of the PMU performance
138 counter available on the system.
139
140 For now, the only calibration implemented is that of the kernel function
141 instrumentation (kretprobes).
142
143 * Calibrate kernel function instrumentation
144
145 Let's use an example to show this calibration. We use an i7 processor with 4
146 general-purpose PMU registers. This information is available by issuing dmesg,
147 looking for "generic registers".
148
149 This sequence of commands will gather a trace executing a kretprobe hooked on
150 an empty function, gathering PMU counters LLC (Last Level Cache) misses
151 information (see lttng add-context \-\-help to see the list of available PMU
152 counters).
153
154 # lttng create calibrate-function
155 # lttng enable-event calibrate \-\-kernel \-\-function lttng_calibrate_kretprobe
156 # lttng add-context \-\-kernel \-t perf:LLC-load-misses \-t perf:LLC-store-misses \\
157 \-t perf:LLC-prefetch-misses
158 # lttng start
159 # for a in $(seq 1 10); do \\
160 lttng calibrate \-\-kernel \-\-function;
161 done
162 # lttng destroy
163 # babeltrace $(ls \-1drt ~/lttng-traces/calibrate-function-* | tail \-n 1)
164
165 The output from babeltrace can be saved to a text file and opened in a
166 spreadsheet (e.g. oocalc) to focus on the per-PMU counter delta between
167 consecutive "calibrate_entry" and "calibrate_return" events. Note that these
168 counters are per-CPU, so scheduling events would need to be present to account
169 for migration between CPU. Therefore, for calibration purposes, only events
170 staying on the same CPU must be considered.
171
172 The average result, for the i7, on 10 samples:
173
174 Average Std.Dev.
175 perf_LLC_load_misses: 5.0 0.577
176 perf_LLC_store_misses: 1.6 0.516
177 perf_LLC_prefetch_misses: 9.0 14.742
178
179 As we can notice, the load and store misses are relatively stable across runs
180 (their standard deviation is relatively low) compared to the prefetch misses.
181 We can conclude from this information that LLC load and store misses can be
182 accounted for quite precisely, but prefetches within a function seems to behave
183 too erratically (not much causality link between the code executed and the CPU
184 prefetch activity) to be accounted for.
185 .fi
186
187 .B OPTIONS:
188
189 .nf
190 \-h, \-\-help
191 Show summary of possible options and commands.
192 \-k, \-\-kernel
193 Apply for the kernel tracer
194 \-u, \-\-userspace
195 Apply for the user-space tracer
196 \-\-function
197 Dynamic function entry/return probe (default)
198 .fi
199
200 .IP
201
202 .IP "\fBcreate\fP [NAME] [OPTIONS]
203 .nf
204 Create tracing session.
205
206 A tracing session contains channel(s) which contains event(s). It is domain
207 agnostic meaning that you can enable channels and events for either the
208 user-space tracer and/or the kernel tracer. It acts like a container
209 aggregating multiple tracing sources.
210
211 On creation, a \fB.lttngrc\fP file is created in your $HOME directory
212 containing the current session name. If NAME is omitted, a session name is
213 automatically created having this form: 'auto-yyyymmdd-hhmmss'.
214
215 If no \fB\-o, \-\-output\fP is specified, the traces will be written in
216 $HOME/lttng-traces.
217 .fi
218
219 .B OPTIONS:
220
221 .nf
222 \-h, \-\-help
223 Show summary of possible options and commands.
224 \-\-list-options
225 Simple listing of options
226 \-o, \-\-output PATH
227 Specify output path for traces
228
229 Using these options, each API call can be controlled individually. For
230 instance, \-C does not enable the consumer automatically. You'll need the \-e
231 option for that.
232
233 \-U, \-\-set-url=URL
234 Set URL for the consumer output destination. It is persistent for the
235 session lifetime. Redo the command to change it. This will set both
236 data and control URL for network.
237 \-C, \-\-ctrl-url=URL
238 Set control path URL. (Must use -D also)
239 \-D, \-\-data-url=URL
240 Set data path URL. (Must use -C also)
241
242 .B URL FORMAT:
243
244 proto://[HOST|IP][:PORT1[:PORT2]][/TRACE_PATH]
245
246 Supported protocols are (proto):
247 > file://...
248 Local filesystem full path.
249
250 > net://...
251 This will use the default network transport layer which is TCP for both
252 control (PORT1) and data port (PORT2). The default ports are
253 respectively 5342 and 5343. Note that net[6]:// is not yet supported.
254
255 > tcp[6]://...
256 Can only be used with -C and -D together
257
258 NOTE: IPv6 address MUST be enclosed in brackets '[]' (rfc2732)
259
260 .B EXAMPLES:
261
262 # lttng create -U net://192.168.1.42
263 Uses TCP and default ports for the given destination.
264
265 # lttng create -U net6://[fe80::f66d:4ff:fe53:d220]
266 Uses TCP, default ports and IPv6.
267
268 # lttng create s1 -U net://myhost.com:3229
269 Create session s1 and set its consumer to myhost.com on port 3229 for control.
270 .fi
271
272 .IP
273
274 .IP "\fBdestroy\fP [OPTIONS] [NAME]"
275 .nf
276 Teardown tracing session
277
278 Free memory on the session daemon and tracer side. It's gone!
279
280 If NAME is omitted, the session name is taken from the .lttngrc file.
281 .fi
282
283 .B OPTIONS:
284
285 .nf
286 \-h, \-\-help
287 Show summary of possible options and commands.
288 \-a, \-\-all
289 Destroy all sessions
290 \-\-list-options
291 Simple listing of options
292 .fi
293
294 .IP
295
296 .IP "\fBenable-channel\fP NAME[,NAME2,...] [-k|-u] [OPTIONS]"
297 .nf
298 Enable tracing channel
299
300 To enable an event, you must enable both the event and the channel that
301 contains it.
302
303 If \fB\-s, \-\-session\fP is omitted, the session name is taken from the .lttngrc
304 file.
305
306 It is important to note that if a certain type of buffers is used, the session
307 will be set with that type and all other subsequent channel need to have the
308 same type.
309 .fi
310
311 .B OPTIONS:
312
313 .nf
314 \-h, \-\-help
315 Show this help
316 \-\-list-options
317 Simple listing of options
318 \-s, \-\-session NAME
319 Apply on session name
320 \-k, \-\-kernel
321 Apply to the kernel tracer
322 \-u, \-\-userspace
323 Apply to the user-space tracer
324
325 \-\-discard
326 Discard event when subbuffers are full (default)
327 \-\-overwrite
328 Flight recorder mode : overwrites events when subbuffers are full
329 \-\-subbuf-size SIZE
330 Subbuffer size in bytes {+k,+M,+G} (default: 4096, kernel default: 262144)
331 Rounded up to the next power of 2.
332 \-\-num-subbuf NUM
333 Number of subbuffers (default: 4)
334 Rounded up to the next power of 2.
335 \-\-switch-timer USEC
336 Switch subbuffer timer interval in ┬Ásec (default: 0)
337 \-\-read-timer USEC
338 Read timer interval in ┬Ásec (UST default: 0, kernel default: 200000)
339 \-\-output TYPE
340 Channel output type. Possible values: mmap, splice
341 \-\-buffers-uid
342 Use per UID buffer (\-u only). Buffers are shared between applications
343 that have the same UID.
344 \-\-buffers-pid
345 Use per PID buffer (\-u only). Each application has its own buffers.
346 \-\-buffers-global
347 Use shared buffer for the whole system (\-k only)
348 \-C, \-\-tracefile-size SIZE
349 Maximum size of each tracefile within a stream (in bytes).
350 \-W, \-\-tracefile-count COUNT
351 Used in conjunction with \-C option, this will limit the number
352 of files created to the specified count.
353
354 .B EXAMPLES:
355
356 $ lttng enable-channel -C 4096 -W 32 chan1
357 For each stream, the maximum size of a trace file will be 4096 bytes divided
358 over a \fBmaximum\fP of 32 different files. The file count is appended after
359 the stream number as seen in the following example. The last trace file is
360 smaller than 4096 since it was not completely filled.
361
362 ~/lttng-traces/[...]/chan1_0_0 (4096)
363 ~/lttng-traces/[...]/chan1_0_1 (4096)
364 ~/lttng-traces/[...]/chan1_0_2 (3245)
365 ~/lttng-traces/[...]/chan1_1_0 (4096)
366 ...
367
368 $ lttng enable-channel -C 4096
369 This will create trace files of 4096 bytes and will create new ones as long as
370 there is data available.
371 .fi
372
373 .IP
374
375 .IP "\fBenable-event\fP NAME[,NAME2,...] [-k|-u] [OPTIONS]"
376 .nf
377 Enable tracing event
378
379 A tracing event is always assigned to a channel. If \fB\-c, \-\-channel\fP is
380 omitted, a default channel named '\fBchannel0\fP' is created and the event is
381 added to it. For the user-space tracer, using \fB\-a, \-\-all\fP is the same as
382 using the wildcard "*".
383
384 If \fB\-s, \-\-session\fP is omitted, the session name is taken from the .lttngrc
385 file.
386 .fi
387
388 .B OPTIONS:
389
390 .nf
391 \-h, \-\-help
392 Show summary of possible options and commands.
393 \-\-list-options
394 Simple listing of options
395 \-s, \-\-session NAME
396 Apply on session name
397 \-c, \-\-channel NAME
398 Apply on channel name
399 \-a, \-\-all
400 Enable all tracepoints and syscalls. This actually enable a single
401 wildcard event "*".
402 \-k, \-\-kernel
403 Apply for the kernel tracer
404 \-u, \-\-userspace
405 Apply for the user-space tracer
406
407 \-\-tracepoint
408 Tracepoint event (default)
409 - userspace tracer supports wildcards at end of string. Don't forget to
410 quote to deal with bash expansion.
411 e.g.:
412 "*"
413 "app_component:na*"
414 \-\-loglevel NAME
415 Tracepoint loglevel range from 0 to loglevel. Listed in the help (\-h).
416 \-\-loglevel-only NAME
417 Tracepoint loglevel (only this loglevel).
418
419 The loglevel or loglevel-only options should be combined with a
420 tracepoint name or tracepoint wildcard.
421 \-\-probe [addr | symbol | symbol+offset]
422 Dynamic probe. Addr and offset can be octal (0NNN...), decimal (NNN...)
423 or hexadecimal (0xNNN...)
424 \-\-function [addr | symbol | symbol+offset]
425 Dynamic function entry/return probe. Addr and offset can be octal
426 (0NNN...), decimal (NNN...) or hexadecimal (0xNNN...)
427 \-\-syscall
428 System call event. Enabling syscalls tracing (kernel tracer), you will
429 not be able to disable them with disable-event. This is a known
430 limitation. You can disable the entire channel to do the trick.
431
432 \-\-filter 'expression'
433 Set a filter on a newly enabled event. Filter expression on event
434 fields and context. Event recording depends on evaluation. Only
435 specify on first activation of a given event within a session.
436 Filter only allowed when enabling events within a session before
437 tracing is started. If the filter fails to link with the event
438 within the traced domain, the event will be discarded.
439 Currently, filter is only implemented for the user-space tracer.
440
441 Expression examples:
442
443 'intfield > 500 && intfield < 503'
444 '(stringfield == "test" || intfield != 10) && intfield > 33'
445 'doublefield > 1.1 && intfield < 5.3'
446
447 Wildcards are allowed at the end of strings:
448 'seqfield1 == "te*"'
449 In string literals, the escape character is a '\\'. Use '\\*' for
450 the '*' character, and '\\\\' for the '\\' character. Wildcard
451 match any sequence of characters, including an empty sub-string
452 (match 0 or more characters).
453
454 Context information can be used for filtering. The examples
455 below show usage of context filtering on process name (with a
456 wildcard), process ID range, and unique thread ID for filtering.
457 The process and thread ID of running applications can be found
458 under columns "PID" and "LWP" of the "ps -eLf" command.
459
460 '$ctx.procname == "demo*"'
461 '$ctx.vpid >= 4433 && $ctx.vpid < 4455'
462 '$ctx.vtid == 1234'
463 .fi
464
465 .IP "\fBdisable-channel\fP NAME[,NAME2,...] [\-k|\-u] [OPTIONS]"
466 .nf
467 Disable tracing channel
468
469 Disabling a channel makes all event(s) in that channel to stop tracing. You can
470 enable it back by calling \fBlttng enable-channel NAME\fP again.
471
472 If \fB\-s, \-\-session\fP is omitted, the session name is taken from the .lttngrc
473 file.
474 .fi
475
476 .B OPTIONS:
477
478 .nf
479 \-h, \-\-help
480 Show summary of possible options and commands.
481 \-\-list-options
482 Simple listing of options
483 \-s, \-\-session NAME
484 Apply on session name
485 \-k, \-\-kernel
486 Apply for the kernel tracer
487 \-u, \-\-userspace
488 Apply for the user-space tracer
489 .fi
490
491 .IP "\fBdisable-event\fP NAME[,NAME2,...] [\-k|\-u] [OPTIONS]"
492 .nf
493 Disable tracing event
494
495 The event, once disabled, can be re-enabled by calling \fBlttng enable-event
496 NAME\fP again.
497
498 If \fB\-s, \-\-session\fP is omitted, the session name is taken from the .lttngrc
499 file.
500 .fi
501
502 .B OPTIONS:
503
504 .nf
505 \-h, \-\-help
506 Show summary of possible options and commands.
507 \-\-list-options
508 Simple listing of options
509 \-s, \-\-session NAME
510 Apply on session name
511 \-a, \-\-all-events
512 Disable all events. This does NOT disable "*" but rather
513 every known events of the session.
514 \-k, \-\-kernel
515 Apply for the kernel tracer
516 \-u, \-\-userspace
517 Apply for the user-space tracer
518 .fi
519
520 .IP "\fBlist\fP [\-k|\-u] [SESSION [SESSION_OPTIONS]]"
521 .nf
522 List tracing session information.
523
524 With no arguments, it will list available tracing session(s).
525
526 With the session name, it will display the details of the session including
527 the trace file path, the associated channels and their state (activated
528 and deactivated), the activated events and more.
529
530 With \-k alone, it will list all available kernel events (except the system
531 calls events).
532 With \-u alone, it will list all available user-space events from registered
533 applications. Here is an example of 'lttng list \-u':
534
535 PID: 7448 - Name: /tmp/lttng-ust/tests/hello/.libs/lt-hello
536 ust_tests_hello:tptest_sighandler (type: tracepoint)
537 ust_tests_hello:tptest (type: tracepoint)
538
539 You can now enable any event listed by using the name :
540 \fBust_tests_hello:tptest\fP.
541 .fi
542
543 .B OPTIONS:
544
545 .nf
546 \-h, \-\-help
547 Show summary of possible options and commands.
548 \-\-list-options
549 Simple listing of options
550 \-k, \-\-kernel
551 Select kernel domain
552 \-u, \-\-userspace
553 Select user-space domain.
554
555 .B SESSION OPTIONS:
556
557 \-c, \-\-channel NAME
558 List details of a channel
559 \-d, \-\-domain
560 List available domain(s)
561 .fi
562
563 .IP "\fBset-session\fP NAME"
564 .nf
565 Set current session name
566
567 Will change the session name in the .lttngrc file.
568 .fi
569
570 .B OPTIONS:
571
572 .nf
573 \-h, \-\-help
574 Show summary of possible options and commands.
575 \-\-list-options
576 Simple listing of options
577 .fi
578
579 .IP
580
581 .IP "\fBstart\fP [NAME] [OPTIONS]"
582 .nf
583 Start tracing
584
585 It will start tracing for all tracers for a specific tracing session.
586
587 If NAME is omitted, the session name is taken from the .lttngrc file.
588 .fi
589
590 .B OPTIONS:
591
592 .nf
593 \-h, \-\-help
594 Show summary of possible options and commands.
595 \-\-list-options
596 Simple listing of options
597 .fi
598
599 .IP
600
601 .IP "\fBstop\fP [NAME] [OPTIONS]"
602 .nf
603 Stop tracing
604
605 It will stop tracing for all tracers for a specific tracing session. Before
606 returning, the command checks for data availability meaning that it will wait
607 until the trace is readable for the session. Use \-\-no-wait to avoid this
608 behavior.
609
610 If NAME is omitted, the session name is taken from the .lttngrc file.
611 .fi
612
613 .B OPTIONS:
614
615 .nf
616 \-h, \-\-help
617 Show summary of possible options and commands.
618 \-\-list-options
619 Simple listing of options
620 \-\-no-wait
621 Don't wait for data availability.
622 .fi
623
624 .IP
625
626 .IP "\fBversion\fP"
627 .nf
628 Show version information
629 .fi
630
631 .B OPTIONS:
632
633 .nf
634 \-h, \-\-help
635 Show summary of possible options and commands.
636 \-\-list-options
637 Simple listing of options
638 .fi
639
640 .IP
641
642 .IP "\fBview\fP [SESSION_NAME] [OPTIONS]"
643 .nf
644 View traces of a tracing session
645
646 By default, the babeltrace viewer will be used for text viewing.
647
648 If SESSION_NAME is omitted, the session name is taken from the .lttngrc file.
649
650 .fi
651
652 .B OPTIONS:
653
654 .nf
655 \-h, \-\-help
656 Show this help
657 \-\-list-options
658 Simple listing of options
659 \-t, \-\-trace-path PATH
660 Trace directory path for the viewer
661 \-e, \-\-viewer CMD
662 Specify viewer and/or options to use
663 This will completely override the default viewers so
664 please make sure to specify the full command. The trace
665 directory path of the session will be appended at the end
666 to the arguments
667 .fi
668
669 .SH "EXIT VALUES"
670 On success 0 is returned and a positive value on error. Value of 1 means a command
671 error, 2 an undefined command, 3 a fatal error and 4 a command warning meaning that
672 something went wrong during the command.
673
674 Any other value above 10, please refer to
675 .BR <lttng/lttng-error.h>
676 for a detailed list or use lttng_strerror() to get a human readable string of
677 the error code.
678
679 .PP
680 .SH "ENVIRONMENT VARIABLES"
681
682 .PP
683 Note that all command line options override environment variables.
684 .PP
685
686 .PP
687 .IP "LTTNG_SESSIOND_PATH"
688 Allows one to specify the full session daemon binary path to lttng command line
689 tool. You can also use \-\-sessiond-path option having the same effect.
690 .SH "SEE ALSO"
691 .BR babeltrace(1),
692 .BR lttng-ust(3),
693 .BR lttng-sessiond(8),
694 .BR lttng-relayd(8),
695 .BR lttng-health-check(3)
696 .SH "BUGS"
697
698 If you encounter any issues or usability problem, please report it on our
699 mailing list <lttng-dev@lists.lttng.org> to help improve this project or
700 at https://bugs.lttng.org which is a bugtracker.
701 .SH "CREDITS"
702
703 .PP
704 lttng is distributed under the GNU General Public License version 2. See the file
705 COPYING for details.
706 .PP
707 A Web site is available at http://lttng.org for more information on the LTTng
708 project.
709 .PP
710 You can also find our git tree at http://git.lttng.org.
711 .PP
712 Mailing lists for support and development: <lttng-dev@lists.lttng.org>.
713 .PP
714 You can find us on IRC server irc.oftc.net (OFTC) in #lttng.
715 .PP
716 .SH "THANKS"
717
718 .PP
719 Thanks to Yannick Brosseau without whom this project would never have been so
720 lean and mean! Also thanks to the Ericsson teams working on tracing which
721 helped us greatly with detailed bug reports and unusual test cases.
722
723 Thanks to our beloved packager Alexandre Montplaisir-Goncalves (Ubuntu and PPA
724 maintainer) and Jon Bernard for our Debian packages.
725
726 Special thanks to Michel Dagenais and the DORSAL laboratory at Polytechnique de
727 Montreal for the LTTng journey.
728 .PP
729 .SH "AUTHORS"
730
731 .PP
732 lttng-tools was originally written by Mathieu Desnoyers, Julien Desfossez and
733 David Goulet. More people have since contributed to it. It is currently
734 maintained by David Goulet <dgoulet@efficios.com>.
735 .PP
This page took 0.0818 seconds and 4 git commands to generate.