| 1 | .TH "LTTNG" "1" "May 13th, 2014" "" "" |
| 2 | |
| 3 | .SH "NAME" |
| 4 | lttng \(em LTTng 2.x tracer control command line tool |
| 5 | |
| 6 | .SH "SYNOPSIS" |
| 7 | |
| 8 | .PP |
| 9 | lttng [OPTIONS] <COMMAND> |
| 10 | .SH "DESCRIPTION" |
| 11 | |
| 12 | .PP |
| 13 | The LTTng project aims at providing highly efficient tracing tools for Linux. |
| 14 | Its tracers help track down performance issues and debug problems |
| 15 | involving multiple concurrent processes and threads. Tracing across multiple |
| 16 | systems is also possible. |
| 17 | |
| 18 | The \fBlttng\fP command line tool from the lttng-tools package is used to control |
| 19 | both kernel and user-space tracing. Every interaction with the tracer should |
| 20 | be done by this tool or by the liblttng-ctl library provided by the lttng-tools |
| 21 | package. |
| 22 | |
| 23 | LTTng uses a session daemon (lttng-sessiond(8)), acting as a tracing registry, |
| 24 | which allows you to interact with multiple tracers (kernel and user-space) |
| 25 | inside the same container, a tracing session. Traces can be gathered from the |
| 26 | kernel and/or instrumented applications (lttng-ust(3)). Aggregating and reading |
| 27 | those traces is done using the babeltrace(1) text viewer. |
| 28 | |
| 29 | We introduce the notion of \fBtracing domains\fP which is essentially a type of |
| 30 | tracer (kernel, user space or JUL for now). In the future, we could see more |
| 31 | tracer like for instance an hypervisor. For some commands, you'll need to |
| 32 | specify on which domain the command operates (\-u, \-k or \-j). For instance, |
| 33 | the kernel domain must be specified when enabling a kernel event. |
| 34 | |
| 35 | In order to trace the kernel, the session daemon needs to be running as root. |
| 36 | LTTng provides the use of a \fBtracing group\fP (default: tracing). Whomever is |
| 37 | in that group can interact with the root session daemon and thus trace the |
| 38 | kernel. Session daemons can co-exist, meaning that you can have a session daemon |
| 39 | running as Alice that can be used to trace her applications along side with a |
| 40 | root daemon or even a Bob daemon. We highly recommend starting the session |
| 41 | daemon at boot time for stable and long term tracing. |
| 42 | |
| 43 | Each user-space application instrumented with lttng-ust(3) will automatically |
| 44 | register with the root session daemon and its user session daemon. This allows |
| 45 | each daemon to list the available traceable applications and tracepoints at any |
| 46 | given moment (See the \fBlist\fP command). |
| 47 | .SH "OPTIONS" |
| 48 | |
| 49 | .PP |
| 50 | This program follow the usual GNU command line syntax with long options starting with |
| 51 | two dashes. Below is a summary of the available options. |
| 52 | .PP |
| 53 | |
| 54 | .TP |
| 55 | .BR "\-h, \-\-help" |
| 56 | Show summary of possible options and commands. |
| 57 | .TP |
| 58 | .BR "\-v, \-\-verbose" |
| 59 | Increase verbosity. |
| 60 | Three levels of verbosity are available which are triggered by putting additional v to |
| 61 | the option (\-vv or \-vvv) |
| 62 | .TP |
| 63 | .BR "\-q, \-\-quiet" |
| 64 | Suppress all messages (even errors). |
| 65 | .TP |
| 66 | .BR "\-g, \-\-group NAME" |
| 67 | Set unix tracing group name. (default: tracing) |
| 68 | .TP |
| 69 | .BR "\-n, \-\-no-sessiond" |
| 70 | Don't automatically spawn a session daemon. |
| 71 | .TP |
| 72 | .BR "\-\-sessiond\-path PATH" |
| 73 | Set session daemon full binary path. |
| 74 | .TP |
| 75 | .BR "\-\-list\-options" |
| 76 | Simple listing of lttng options. |
| 77 | .TP |
| 78 | .BR "\-\-list\-commands" |
| 79 | Simple listing of lttng commands. |
| 80 | .SH "COMMANDS" |
| 81 | |
| 82 | .PP |
| 83 | \fBadd-context\fP [OPTIONS] |
| 84 | .RS |
| 85 | Add context to event(s) and/or channel(s). |
| 86 | |
| 87 | A context is basically extra information appended to a channel. For instance, |
| 88 | you could ask the tracer to add the PID information for all events in a |
| 89 | channel. You can also add performance monitoring unit counters (perf PMU) using |
| 90 | the perf kernel API. |
| 91 | |
| 92 | For example, this command will add the context information 'prio' and two per-CPU |
| 93 | perf counters (hardware branch misses and cache misses), to all events in the trace |
| 94 | data output: |
| 95 | |
| 96 | .nf |
| 97 | # lttng add-context \-k \-t prio \-t perf:cpu:branch-misses \\ |
| 98 | \-t perf:cpu:cache-misses |
| 99 | .fi |
| 100 | |
| 101 | Please take a look at the help (\-h/\-\-help) for a detailed list of available |
| 102 | contexts. |
| 103 | |
| 104 | Perf counters are available as per-CPU ("perf:cpu:...") and per-thread |
| 105 | ("perf:thread:...") counters. Currently, per-CPU counters can only be |
| 106 | used with the kernel tracing domain, and per-thread counters can only be |
| 107 | used with the UST tracing domain. |
| 108 | |
| 109 | If no channel is given (\-c), the context is added to all channels that were |
| 110 | already enabled. If the session has no channel, a default channel is created. |
| 111 | Otherwise the context will be added only to the given channel (\-c). |
| 112 | |
| 113 | If \fB\-s, \-\-session\fP is omitted, the session name is taken from the .lttngrc |
| 114 | file. |
| 115 | |
| 116 | .B OPTIONS: |
| 117 | |
| 118 | .TP |
| 119 | .BR "\-h, \-\-help" |
| 120 | Show summary of possible options and commands. |
| 121 | .TP |
| 122 | .BR "\-s, \-\-session NAME" |
| 123 | Apply on session name. |
| 124 | .TP |
| 125 | .BR "\-c, \-\-channel NAME" |
| 126 | Apply on channel name. |
| 127 | .TP |
| 128 | .BR "\-k, \-\-kernel" |
| 129 | Apply for the kernel tracer |
| 130 | .TP |
| 131 | .BR "\-u, \-\-userspace" |
| 132 | Apply for the user-space tracer |
| 133 | .TP |
| 134 | .BR "\-t, \-\-type TYPE" |
| 135 | Context type. You can repeat this option on the command line. Please |
| 136 | use "lttng add-context \-h" to list all available types. |
| 137 | .RE |
| 138 | .PP |
| 139 | |
| 140 | .PP |
| 141 | \fBcalibrate\fP [OPTIONS] |
| 142 | .RS |
| 143 | Quantify LTTng overhead |
| 144 | |
| 145 | The LTTng calibrate command can be used to find out the combined average |
| 146 | overhead of the LTTng tracer and the instrumentation mechanisms used. This |
| 147 | overhead can be calibrated in terms of time or using any of the PMU performance |
| 148 | counter available on the system. |
| 149 | |
| 150 | For now, the only calibration implemented is that of the kernel function |
| 151 | instrumentation (kretprobes). |
| 152 | |
| 153 | * Calibrate kernel function instrumentation |
| 154 | |
| 155 | Let's use an example to show this calibration. We use an i7 processor with 4 |
| 156 | general-purpose PMU registers. This information is available by issuing dmesg, |
| 157 | looking for "generic registers". |
| 158 | |
| 159 | This sequence of commands will gather a trace executing a kretprobe hooked on |
| 160 | an empty function, gathering PMU counters LLC (Last Level Cache) misses |
| 161 | information (see lttng add-context \-\-help to see the list of available PMU |
| 162 | counters). |
| 163 | |
| 164 | .nf |
| 165 | # lttng create calibrate-function |
| 166 | # lttng enable-event calibrate \-\-kernel \\ |
| 167 | \-\-function lttng_calibrate_kretprobe |
| 168 | # lttng add-context \-\-kernel \-t perf:cpu:LLC-load-misses \\ |
| 169 | \-t perf:cpu:LLC-store-misses \\ |
| 170 | \-t perf:cpu:LLC-prefetch-misses |
| 171 | # lttng start |
| 172 | # for a in $(seq 1 10); do \\ |
| 173 | lttng calibrate \-\-kernel \-\-function; |
| 174 | done |
| 175 | # lttng destroy |
| 176 | # babeltrace $(ls \-1drt ~/lttng-traces/calibrate-function-* \\ |
| 177 | | tail \-n 1) |
| 178 | .fi |
| 179 | |
| 180 | The output from babeltrace can be saved to a text file and opened in a |
| 181 | spreadsheet (e.g. oocalc) to focus on the per-PMU counter delta between |
| 182 | consecutive "calibrate_entry" and "calibrate_return" events. Note that these |
| 183 | counters are per-CPU, so scheduling events would need to be present to account |
| 184 | for migration between CPU. Therefore, for calibration purposes, only events |
| 185 | staying on the same CPU must be considered. |
| 186 | |
| 187 | The average result, for the i7, on 10 samples: |
| 188 | |
| 189 | .nf |
| 190 | Average Std.Dev. |
| 191 | perf_LLC_load_misses: 5.0 0.577 |
| 192 | perf_LLC_store_misses: 1.6 0.516 |
| 193 | perf_LLC_prefetch_misses: 9.0 14.742 |
| 194 | .fi |
| 195 | |
| 196 | As we can notice, the load and store misses are relatively stable across runs |
| 197 | (their standard deviation is relatively low) compared to the prefetch misses. |
| 198 | We can conclude from this information that LLC load and store misses can be |
| 199 | accounted for quite precisely, but prefetches within a function seems to behave |
| 200 | too erratically (not much causality link between the code executed and the CPU |
| 201 | prefetch activity) to be accounted for. |
| 202 | |
| 203 | .B OPTIONS: |
| 204 | |
| 205 | .TP |
| 206 | .BR "\-h, \-\-help" |
| 207 | Show summary of possible options and commands. |
| 208 | .TP |
| 209 | .BR "\-k, \-\-kernel" |
| 210 | Apply for the kernel tracer |
| 211 | .TP |
| 212 | .BR "\-u, \-\-userspace" |
| 213 | Apply for the user-space tracer |
| 214 | .TP |
| 215 | .BR "\-\-function" |
| 216 | Dynamic function entry/return probe (default) |
| 217 | .RE |
| 218 | .PP |
| 219 | |
| 220 | .PP |
| 221 | \fBcreate\fP [NAME] [OPTIONS] |
| 222 | .RS |
| 223 | Create tracing session. |
| 224 | |
| 225 | A tracing session contains channel(s) which contains event(s). It is domain |
| 226 | agnostic, meaning that channels and events can be enabled for the |
| 227 | user-space tracer and/or the kernel tracer. It acts like a container |
| 228 | aggregating multiple tracing sources. |
| 229 | |
| 230 | On creation, a \fB.lttngrc\fP file is created in your $HOME directory |
| 231 | containing the current session name. If NAME is omitted, a session name is |
| 232 | automatically created having this form: 'auto-yyyymmdd-hhmmss'. |
| 233 | |
| 234 | If no \fB\-o, \-\-output\fP is specified, the traces will be written in |
| 235 | $HOME/lttng-traces. |
| 236 | |
| 237 | The $HOME environment variable can be overridden by defining the environment |
| 238 | variable LTTNG_HOME. This is useful when the user running the commands has |
| 239 | a non-writeable home directory. |
| 240 | |
| 241 | The session name MUST NOT contain the character '/'. |
| 242 | |
| 243 | .B OPTIONS: |
| 244 | |
| 245 | .TP |
| 246 | .BR "\-h, \-\-help" |
| 247 | Show summary of possible options and commands. |
| 248 | .TP |
| 249 | .BR "\-\-list-options" |
| 250 | Simple listing of options |
| 251 | .TP |
| 252 | .BR "\-o, \-\-output PATH" |
| 253 | Specify output path for traces |
| 254 | .TP |
| 255 | .BR "\-\-no-output" |
| 256 | Traces will not be output |
| 257 | .TP |
| 258 | .BR "\-\-snapshot" |
| 259 | Set the session in snapshot mode. Created in no-output mode and uses the |
| 260 | URL, if one is specified, as the default snapshot output. Every channel will be set |
| 261 | in overwrite mode and with mmap output (splice not supported). |
| 262 | .TP |
| 263 | .BR "\-\-live [USEC]" |
| 264 | Set the session exclusively in live mode. The paremeter is the delay in micro |
| 265 | seconds before the data is flushed and streamed. The live mode allows you to |
| 266 | stream the trace and view it while it's being recorded by any tracer. For that, |
| 267 | you need a lttng-relayd and this session requires a network URL (\-U or |
| 268 | \-C/\-D). If no USEC nor URL is provided, the default is to use a timer value |
| 269 | set to 1000000 and the network URL set to net://127.0.0.1. |
| 270 | |
| 271 | To read a live session, you can use babeltrace(1) or the live streaming |
| 272 | protocol in doc/live-reading-protocol.txt. Here is an example: |
| 273 | |
| 274 | .nf |
| 275 | $ lttng-relayd -o /tmp/lttng |
| 276 | $ lttng create --live 200000 -U net://localhost |
| 277 | $ lttng enable-event -a --userspace |
| 278 | $ lttng start |
| 279 | .fi |
| 280 | |
| 281 | After the start, you'll be able to read the events while they are being |
| 282 | recorded in /tmp/lttng. |
| 283 | |
| 284 | .TP |
| 285 | .BR "\-U, \-\-set-url=URL" |
| 286 | Set URL for the consumer output destination. It is persistent for the |
| 287 | session lifetime. Redo the command to change it. This will set both data |
| 288 | and control URL for network. |
| 289 | .TP |
| 290 | .BR "\-C, \-\-ctrl-url=URL" |
| 291 | Set control path URL. (Must use -D also) |
| 292 | .TP |
| 293 | .BR "\-D, \-\-data-url=URL" |
| 294 | Set data path URL. (Must use -C also) |
| 295 | .PP |
| 296 | Using these options, each API call can be controlled individually. For |
| 297 | instance, \-C does not enable the consumer automatically. You'll need the \-e |
| 298 | option for that. |
| 299 | |
| 300 | .B URL FORMAT: |
| 301 | |
| 302 | proto://[HOST|IP][:PORT1[:PORT2]][/TRACE_PATH] |
| 303 | |
| 304 | Supported protocols are (proto): |
| 305 | .TP |
| 306 | .BR "file://..." |
| 307 | Local filesystem full path. |
| 308 | |
| 309 | .TP |
| 310 | .BR "net://..." |
| 311 | This will use the default network transport layer which is TCP for both |
| 312 | control (PORT1) and data port (PORT2). The default ports are |
| 313 | respectively 5342 and 5343. Note that net[6]:// is not yet supported. |
| 314 | |
| 315 | .TP |
| 316 | .BR "tcp[6]://..." |
| 317 | Can only be used with -C and -D together |
| 318 | |
| 319 | NOTE: IPv6 address MUST be enclosed in brackets '[]' (rfc2732) |
| 320 | |
| 321 | .B EXAMPLES: |
| 322 | |
| 323 | .nf |
| 324 | # lttng create -U net://192.168.1.42 |
| 325 | .fi |
| 326 | Uses TCP and default ports for the given destination. |
| 327 | |
| 328 | .nf |
| 329 | # lttng create -U net6://[fe80::f66d:4ff:fe53:d220] |
| 330 | .fi |
| 331 | Uses TCP, default ports and IPv6. |
| 332 | |
| 333 | .nf |
| 334 | # lttng create s1 -U net://myhost.com:3229 |
| 335 | .fi |
| 336 | Create session s1 and set its consumer to myhost.com on port 3229 for control. |
| 337 | .RE |
| 338 | .PP |
| 339 | |
| 340 | .PP |
| 341 | \fBdestroy\fP [NAME] [OPTIONS] |
| 342 | .RS |
| 343 | Teardown tracing session |
| 344 | |
| 345 | Free memory on the session daemon and tracer side. It's gone! |
| 346 | |
| 347 | If NAME is omitted, the session name is taken from the .lttngrc file. |
| 348 | |
| 349 | .B OPTIONS: |
| 350 | |
| 351 | .TP |
| 352 | .BR "\-h, \-\-help" |
| 353 | Show summary of possible options and commands. |
| 354 | .TP |
| 355 | .BR "\-a, \-\-all" |
| 356 | Destroy all sessions |
| 357 | .TP |
| 358 | .BR "\-\-list-options" |
| 359 | Simple listing of options |
| 360 | .RE |
| 361 | .PP |
| 362 | |
| 363 | .PP |
| 364 | \fBenable-channel\fP NAME[,NAME2,...] (\-k | \-u) [OPTIONS] |
| 365 | .RS |
| 366 | Enable tracing channel |
| 367 | |
| 368 | To enable an event, you must enable both the event and the channel that |
| 369 | contains it. |
| 370 | |
| 371 | If \fB\-s, \-\-session\fP is omitted, the session name is taken from the .lttngrc |
| 372 | file. |
| 373 | |
| 374 | Exactly one of \-k or -u must be specified. |
| 375 | |
| 376 | It is important to note that if a certain type of buffers is used, the session |
| 377 | will be set with that type and all other subsequent channel needs to have the |
| 378 | same type. |
| 379 | |
| 380 | Note that once the session has been started and enabled on the tracer side, |
| 381 | it's not possible anymore to enable a new channel for that session. |
| 382 | |
| 383 | .B OPTIONS: |
| 384 | |
| 385 | .TP |
| 386 | .BR "\-h, \-\-help" |
| 387 | Show this help |
| 388 | .TP |
| 389 | .BR "\-\-list-options" |
| 390 | Simple listing of options |
| 391 | .TP |
| 392 | .BR "\-s, \-\-session NAME" |
| 393 | Apply on session name |
| 394 | .TP |
| 395 | .BR "\-k, \-\-kernel" |
| 396 | Apply to the kernel tracer |
| 397 | .TP |
| 398 | .BR "\-u, \-\-userspace" |
| 399 | Apply to the user-space tracer |
| 400 | .TP |
| 401 | .BR "\-\-discard" |
| 402 | Discard event when subbuffers are full (default) |
| 403 | .TP |
| 404 | .BR "\-\-overwrite" |
| 405 | Flight recorder mode: overwrites events when subbuffers are full. The |
| 406 | number of subbuffer must be 2 or more. |
| 407 | .TP |
| 408 | .BR "\-\-subbuf-size SIZE" |
| 409 | Subbuffer size in bytes {+k,+M,+G}. |
| 410 | (default UST uid: 131072, UST pid: 4096, kernel: 262144, metadata: 4096) |
| 411 | Rounded up to the next power of 2. |
| 412 | |
| 413 | The minimum subbuffer size, for each tracer, is the max value between |
| 414 | the default above and the system page size. You can issue this command |
| 415 | to get the current page size on your system: \fB$ getconf PAGE_SIZE\fP |
| 416 | .TP |
| 417 | .BR "\-\-num-subbuf NUM" |
| 418 | Number of subbuffers. (default UST uid: 4, UST pid: 4, kernel: 4, |
| 419 | metadata: 2) Rounded up to the next power of 2. |
| 420 | .TP |
| 421 | .BR "\-\-switch-timer USEC" |
| 422 | Switch subbuffer timer interval in µsec. |
| 423 | (default UST uid: 0, UST pid: 0, kernel: 0, metadata: 0) |
| 424 | .TP |
| 425 | .BR "\-\-read-timer USEC" |
| 426 | Read timer interval in µsec. |
| 427 | (default UST uid: 0, UST pid: 0, kernel: 200000, metadata: 0) |
| 428 | .TP |
| 429 | .BR "\-\-output TYPE" |
| 430 | Channel output type. Possible values: mmap, splice |
| 431 | (default UST uid: mmap, UST pid: mmap, kernel: splice, metadata: mmap) |
| 432 | .TP |
| 433 | .BR "\-\-buffers-uid" |
| 434 | Use per UID buffer (\-u only). Buffers are shared between applications |
| 435 | that have the same UID. |
| 436 | .TP |
| 437 | .BR "\-\-buffers-pid" |
| 438 | Use per PID buffer (\-u only). Each application has its own buffers. |
| 439 | .TP |
| 440 | .BR "\-\-buffers-global" |
| 441 | Use shared buffer for the whole system (\-k only) |
| 442 | .TP |
| 443 | .BR "\-C, \-\-tracefile-size SIZE" |
| 444 | Maximum size of each tracefile within a stream (in bytes). |
| 445 | 0 means unlimited. (default: 0) |
| 446 | Note: traces generated with this option may inaccurately report |
| 447 | discarded events as of CTF 1.8. |
| 448 | .TP |
| 449 | .BR "\-W, \-\-tracefile-count COUNT" |
| 450 | Used in conjunction with \-C option, this will limit the number of files |
| 451 | created to the specified count. 0 means unlimited. (default: 0) |
| 452 | |
| 453 | .B EXAMPLES: |
| 454 | |
| 455 | .nf |
| 456 | $ lttng enable-channel -k -C 4096 -W 32 chan1 |
| 457 | .fi |
| 458 | For each stream, the maximum size of each trace file will be 4096 bytes and |
| 459 | there will be a maximum of 32 different files. The file count is appended after |
| 460 | the stream number as seen in the following example. The last trace file is |
| 461 | smaller than 4096 since it was not completely filled. |
| 462 | |
| 463 | .nf |
| 464 | ~/lttng-traces/[...]/chan1_0_0 (4096) |
| 465 | ~/lttng-traces/[...]/chan1_0_1 (4096) |
| 466 | ~/lttng-traces/[...]/chan1_0_2 (3245) |
| 467 | ~/lttng-traces/[...]/chan1_1_0 (4096) |
| 468 | ... |
| 469 | .fi |
| 470 | |
| 471 | .nf |
| 472 | $ lttng enable-channel -k -C 4096 |
| 473 | .fi |
| 474 | This will create trace files of 4096 bytes and will create new ones as long as |
| 475 | there is data available. |
| 476 | .RE |
| 477 | .PP |
| 478 | |
| 479 | .PP |
| 480 | \fBenable-event\fP NAME[,NAME2,...] [-k|-u] [OPTIONS] |
| 481 | .RS |
| 482 | Enable tracing event |
| 483 | |
| 484 | A tracing event is always assigned to a channel. If \fB\-c, \-\-channel\fP is |
| 485 | omitted, a default channel named '\fBchannel0\fP' is created and the event is |
| 486 | added to it. If \fB\-c, \-\-channel\fP is omitted, but a non-default |
| 487 | channel already exists within the session, an error is returned. For the |
| 488 | user-space tracer, using \fB\-a, \-\-all\fP is the same as using the |
| 489 | wildcard "*". |
| 490 | |
| 491 | If \fB\-s, \-\-session\fP is omitted, the session name is taken from the .lttngrc |
| 492 | file. |
| 493 | |
| 494 | .B OPTIONS: |
| 495 | |
| 496 | .TP |
| 497 | .BR "\-h, \-\-help" |
| 498 | Show summary of possible options and commands. |
| 499 | .TP |
| 500 | .BR "\-\-list-options" |
| 501 | Simple listing of options |
| 502 | .TP |
| 503 | .BR "\-s, \-\-session NAME" |
| 504 | Apply on session name |
| 505 | .TP |
| 506 | .BR "\-c, \-\-channel NAME" |
| 507 | Apply on channel name |
| 508 | .TP |
| 509 | .BR "\-a, \-\-all" |
| 510 | Enable all tracepoints and syscalls. This actually enables a single |
| 511 | wildcard event "*". |
| 512 | .TP |
| 513 | .BR "\-k, \-\-kernel" |
| 514 | Apply for the kernel tracer |
| 515 | .TP |
| 516 | .BR "\-u, \-\-userspace" |
| 517 | Apply for the user-space tracer |
| 518 | .TP |
| 519 | .BR "\-j, \-\-jul" |
| 520 | Apply for Java application using Java Util Logging interface (JUL) |
| 521 | .TP |
| 522 | .BR "\-\-tracepoint" |
| 523 | Tracepoint event (default). Userspace tracer supports wildcards at the end |
| 524 | of string. Don't forget to quote to deal with bash expansion. |
| 525 | e.g.: |
| 526 | .nf |
| 527 | "*" |
| 528 | "app_component:na*" |
| 529 | .fi |
| 530 | .TP |
| 531 | .BR "\-\-loglevel NAME" |
| 532 | Tracepoint loglevel range from 0 to loglevel. Listed in the help (\-h). |
| 533 | For the JUL domain, the loglevel ranges are detailed with the \-\-help |
| 534 | option thus starting from SEVERE to FINEST. |
| 535 | .TP |
| 536 | .BR "\-\-loglevel-only NAME" |
| 537 | Tracepoint loglevel (only this loglevel). |
| 538 | The loglevel or loglevel-only options should be combined with a |
| 539 | tracepoint name or tracepoint wildcard. |
| 540 | .TP |
| 541 | .BR "\-\-probe (addr | symbol | symbol+offset)" |
| 542 | Dynamic probe. Addr and offset can be octal (0NNN...), decimal (NNN...) |
| 543 | or hexadecimal (0xNNN...) |
| 544 | .TP |
| 545 | .BR "\-\-function (addr | symbol | symbol+offset)" |
| 546 | Dynamic function entry/return probe. Addr and offset can be octal |
| 547 | (0NNN...), decimal (NNN...) or hexadecimal (0xNNN...) |
| 548 | .TP |
| 549 | .BR "\-\-syscall" |
| 550 | System call event. Enabling syscalls tracing (kernel tracer), you will |
| 551 | not be able to disable them with disable-event. This is a known |
| 552 | limitation. You can disable the entire channel to do the trick. Also note |
| 553 | that per-syscall selection is not supported yet. Use with "-a" to enable |
| 554 | all syscalls. |
| 555 | .TP |
| 556 | .BR "\-\-filter 'expression'" |
| 557 | Set a filter on a newly enabled event. Filter expression on event |
| 558 | fields and context. The event will be recorded if the filter's |
| 559 | expression evaluates to TRUE. Only specify on first activation of a |
| 560 | given event within a session. |
| 561 | Specifying a filter is only allowed when enabling events within a session before |
| 562 | tracing is started. If the filter fails to link with the event |
| 563 | within the traced domain, the event will be discarded. |
| 564 | Filtering is currently only implemented for the user-space tracer. |
| 565 | |
| 566 | Expression examples: |
| 567 | |
| 568 | .nf |
| 569 | 'intfield > 500 && intfield < 503' |
| 570 | '(strfield == "test" || intfield != 10) && intfield > 33' |
| 571 | 'doublefield > 1.1 && intfield < 5.3' |
| 572 | .fi |
| 573 | |
| 574 | Wildcards are allowed at the end of strings: |
| 575 | 'seqfield1 == "te*"' |
| 576 | In string literals, the escape character is a '\\'. Use '\\*' for |
| 577 | the '*' character, and '\\\\' for the '\\' character sequence. Wildcard |
| 578 | matches any sequence of characters, including an empty sub-string |
| 579 | (matches 0 or more characters). |
| 580 | |
| 581 | Context information can be used for filtering. The examples below shows |
| 582 | usage of context filtering on the process name (using a wildcard), process ID |
| 583 | range, and unique thread ID. The process and thread IDs of |
| 584 | running applications can be found under columns "PID" and "LWP" of the |
| 585 | "ps -eLf" command. |
| 586 | |
| 587 | .nf |
| 588 | '$ctx.procname == "demo*"' |
| 589 | '$ctx.vpid >= 4433 && $ctx.vpid < 4455' |
| 590 | '$ctx.vtid == 1234' |
| 591 | .fi |
| 592 | |
| 593 | Context information is available to all filters whether or not the add-context |
| 594 | command has been used to add it to the event's channel, as long as the context |
| 595 | field exists for that domain. For example, the filter examples given above will |
| 596 | never fail to link: no add-context is required for the event's channel. |
| 597 | |
| 598 | .TP |
| 599 | .BR "\-x, \-\-exclude LIST" |
| 600 | Add exclusions to UST tracepoints: |
| 601 | Events that match any of the items in the comma-separated LIST are not |
| 602 | enabled, even if they match a wildcard definition of the event. |
| 603 | |
| 604 | This option is also applicable with the \fB\-a, \-\-all\fP option, |
| 605 | in which case all UST tracepoints are enabled except the ones whose |
| 606 | names match any of the items in LIST. |
| 607 | .RE |
| 608 | .PP |
| 609 | |
| 610 | .PP |
| 611 | \fBdisable-channel\fP NAME[,NAME2,...] (\-k | \-u) [OPTIONS] |
| 612 | .RS |
| 613 | Disable tracing channel |
| 614 | |
| 615 | Disabling a channel disables the tracing of all of the channel's events. A channel |
| 616 | can be re-enabled by calling \fBlttng enable-channel NAME\fP again. |
| 617 | |
| 618 | If \fB\-s, \-\-session\fP is omitted, the session name is taken from the .lttngrc |
| 619 | file. |
| 620 | |
| 621 | .B OPTIONS: |
| 622 | |
| 623 | .TP |
| 624 | .BR "\-h, \-\-help" |
| 625 | Show summary of possible options and commands. |
| 626 | .TP |
| 627 | .BR "\-\-list-options" |
| 628 | Simple listing of options |
| 629 | .TP |
| 630 | .BR "\-s, \-\-session NAME" |
| 631 | Apply on session name |
| 632 | .TP |
| 633 | .BR "\-k, \-\-kernel" |
| 634 | Apply for the kernel tracer |
| 635 | .TP |
| 636 | .BR "\-u, \-\-userspace" |
| 637 | Apply for the user-space tracer |
| 638 | .RE |
| 639 | .PP |
| 640 | |
| 641 | .PP |
| 642 | \fBdisable-event\fP NAME[,NAME2,...] (\-k | \-u) [OPTIONS] |
| 643 | .RS |
| 644 | Disable tracing event |
| 645 | |
| 646 | The event, once disabled, can be re-enabled by calling \fBlttng enable-event |
| 647 | NAME\fP again. |
| 648 | |
| 649 | If \fB\-s, \-\-session\fP is omitted, the session name is taken from the .lttngrc |
| 650 | file. |
| 651 | |
| 652 | If \fB\-c, \-\-channel\fP is omitted, the default channel name is used. |
| 653 | If \fB\-c, \-\-channel\fP is omitted, but a non-default channel already |
| 654 | exists within the session, an error is returned. |
| 655 | |
| 656 | .B OPTIONS: |
| 657 | |
| 658 | .TP |
| 659 | .BR "\-h, \-\-help" |
| 660 | Show summary of possible options and commands. |
| 661 | .TP |
| 662 | .BR "\-\-list-options" |
| 663 | Simple listing of options |
| 664 | .TP |
| 665 | .BR "\-s, \-\-session NAME" |
| 666 | Apply on session name |
| 667 | .TP |
| 668 | .BR "\-c, \-\-channel NAME" |
| 669 | Apply on channel name |
| 670 | .TP |
| 671 | .BR "\-a, \-\-all-events" |
| 672 | Disable all events. This does NOT disable "*" but rather every known |
| 673 | events of the session. |
| 674 | .TP |
| 675 | .BR "\-k, \-\-kernel" |
| 676 | Apply for the kernel tracer |
| 677 | .TP |
| 678 | .BR "\-u, \-\-userspace" |
| 679 | Apply for the user-space tracer |
| 680 | .TP |
| 681 | .BR "\-j, \-\-jul" |
| 682 | Apply for Java application using Java Util Logging interface (JUL) |
| 683 | .RE |
| 684 | .PP |
| 685 | |
| 686 | .PP |
| 687 | \fBlist\fP [OPTIONS] [SESSION [SESSION OPTIONS]] |
| 688 | .RS |
| 689 | List tracing session information. |
| 690 | |
| 691 | With no arguments, it will list available tracing session(s). |
| 692 | |
| 693 | With the session name, it will display the details of the session including |
| 694 | the trace file path, the associated channels and their state (activated |
| 695 | and deactivated), the activated events and more. |
| 696 | |
| 697 | With \-k alone, it will list all available kernel events (except the system |
| 698 | calls events). |
| 699 | With \-j alone, the available JUL event from registered application will be |
| 700 | list. The event corresponds to the Logger name in the Java JUL application. |
| 701 | With \-u alone, it will list all available user-space events from registered |
| 702 | applications. Here is an example of 'lttng list \-u': |
| 703 | |
| 704 | .nf |
| 705 | PID: 7448 - Name: /tmp/lttng-ust/tests/hello/.libs/lt-hello |
| 706 | ust_tests_hello:tptest_sighandler (type: tracepoint) |
| 707 | ust_tests_hello:tptest (type: tracepoint) |
| 708 | .fi |
| 709 | |
| 710 | You can now enable any event listed by using the name : |
| 711 | \fBust_tests_hello:tptest\fP. |
| 712 | |
| 713 | .B OPTIONS: |
| 714 | |
| 715 | .TP |
| 716 | .BR "\-h, \-\-help" |
| 717 | Show summary of possible options and commands. |
| 718 | .TP |
| 719 | .BR "\-\-list-options" |
| 720 | Simple listing of options |
| 721 | .TP |
| 722 | .BR "\-k, \-\-kernel" |
| 723 | Select kernel domain |
| 724 | .TP |
| 725 | .BR "\-u, \-\-userspace" |
| 726 | Select user-space domain. |
| 727 | .TP |
| 728 | .BR "\-j, \-\-jul" |
| 729 | Apply for Java application using JUL |
| 730 | .TP |
| 731 | .BR "\-f, \-\-fields" |
| 732 | List event fields |
| 733 | |
| 734 | .PP |
| 735 | .B SESSION OPTIONS: |
| 736 | |
| 737 | .TP |
| 738 | .BR "\-c, \-\-channel NAME" |
| 739 | List details of a channel |
| 740 | .TP |
| 741 | .BR "\-d, \-\-domain" |
| 742 | List available domain(s) |
| 743 | .RE |
| 744 | .PP |
| 745 | |
| 746 | .PP |
| 747 | \fBload\fP [OPTIONS] [NAME] |
| 748 | .RS |
| 749 | Load tracing session configuration |
| 750 | |
| 751 | If NAME is omitted, all session configurations found in both the user's session |
| 752 | configuration directory (default: ~/.lttng/sessions/) and the system session |
| 753 | configuration directory (default: /etc/lttng/sessions/) will be loaded. Note |
| 754 | that the sessions in the user directory are loaded first and then the system |
| 755 | wide directory are loaded. |
| 756 | |
| 757 | .B OPTIONS: |
| 758 | |
| 759 | .TP |
| 760 | .BR "\-h, \-\-help" |
| 761 | Show summary of possible options and commands. |
| 762 | .TP |
| 763 | .BR "\-a, \-\-all" |
| 764 | Load all session configurations (default). |
| 765 | .TP |
| 766 | .BR "\-i, \-\-input-path PATH" |
| 767 | Specify the input path for session configurations. This overrides the default |
| 768 | session configuration directory. |
| 769 | .TP |
| 770 | .BR "\-f, -\-force" |
| 771 | Overwrite current session configuration(s) if a session of the same name |
| 772 | already exists. |
| 773 | .RE |
| 774 | .PP |
| 775 | |
| 776 | .PP |
| 777 | \fBsave\fP [OPTIONS] [SESSION] |
| 778 | .RS |
| 779 | Save tracing session configuration |
| 780 | |
| 781 | If SESSION is omitted, all session configurations will be saved to individual |
| 782 | \fB.lttng\fP files under the user's session configuration directory (default: |
| 783 | ~/.lttng/sessions/). The default session configuration file naming scheme is |
| 784 | \fBSESSION.lttng\fP. |
| 785 | |
| 786 | For instance, a user in the tracing group saving a session from a root session |
| 787 | daemon will save it in her/his user directory. |
| 788 | |
| 789 | .B OPTIONS: |
| 790 | |
| 791 | .TP |
| 792 | .BR "\-h, \-\-help" |
| 793 | Show summary of possible options and commands. |
| 794 | .TP |
| 795 | .BR "\-a, \-\-all" |
| 796 | Save all session configurations (default). |
| 797 | .TP |
| 798 | .BR "\-o, \-\-output-path PATH" |
| 799 | Specify the output path for saved sessions. This overrides the default session |
| 800 | configuration directory. |
| 801 | .TP |
| 802 | .BR "\-f, -\-force" |
| 803 | Overwrite session configuration file if session name clashes. |
| 804 | .RE |
| 805 | .PP |
| 806 | |
| 807 | .PP |
| 808 | \fBset-session\fP NAME [OPTIONS] |
| 809 | .RS |
| 810 | Set current session name |
| 811 | |
| 812 | Will change the session name in the .lttngrc file. |
| 813 | |
| 814 | .B OPTIONS: |
| 815 | |
| 816 | .TP |
| 817 | .BR "\-h, \-\-help" |
| 818 | Show summary of possible options and commands. |
| 819 | .TP |
| 820 | .BR "\-\-list-options" |
| 821 | Simple listing of options |
| 822 | .RE |
| 823 | .PP |
| 824 | |
| 825 | .PP |
| 826 | \fBsnapshot\fP [OPTIONS] ACTION |
| 827 | .RS |
| 828 | Snapshot command for LTTng session. |
| 829 | |
| 830 | .B OPTIONS: |
| 831 | |
| 832 | .TP |
| 833 | .BR "\-h, \-\-help" |
| 834 | Show summary of possible options and commands. |
| 835 | .TP |
| 836 | .BR "\-\-list-options" |
| 837 | Simple listing of options |
| 838 | |
| 839 | .PP |
| 840 | .B ACTION: |
| 841 | |
| 842 | .TP |
| 843 | \fBadd-output\fP [-m <SIZE>] [-s <NAME>] [-n <NAME>] <URL> | -C <URL> -D <URL> |
| 844 | |
| 845 | Setup and add an snapshot output for a session. Output are the destination |
| 846 | where the snapshot will be sent. Only one output is permitted. To change it, |
| 847 | you'll need to delete it and add back the new one. |
| 848 | |
| 849 | .TP |
| 850 | \fBdel-output\fP ID | NAME [-s <NAME>] |
| 851 | |
| 852 | Delete an output for a session using the ID. You can either specify the |
| 853 | output's ID that can be found with list-output or the name. |
| 854 | |
| 855 | .TP |
| 856 | \fBlist-output\fP [-s <NAME>] |
| 857 | |
| 858 | List the output of a session. Attributes of the output are printed. |
| 859 | |
| 860 | .TP |
| 861 | \fBrecord\fP [-m <SIZE>] [-s <NAME>] [-n <NAME>] [<URL> | -C <URL> -D <URL>] |
| 862 | |
| 863 | Snapshot a session's buffer(s) for all domains. If an URL is specified, it is |
| 864 | used instead of a previously added output. Specifying only a name or/and a max |
| 865 | size will override the current output values. For instance, you can record a |
| 866 | snapshot with a custom maximum size or with a different name. |
| 867 | |
| 868 | .nf |
| 869 | $ lttng snapshot add-output -n mysnapshot file:///data/snapshot |
| 870 | [...] |
| 871 | $ lttng snapshot record -n new_name_snapshot |
| 872 | .fi |
| 873 | |
| 874 | The above will create a snapshot in /data/snapshot/new_name_snapshot* directory |
| 875 | rather then in mysnapshot*/ |
| 876 | |
| 877 | .PP |
| 878 | .B DETAILED ACTION OPTIONS |
| 879 | |
| 880 | .TP |
| 881 | .BR "\-s, \-\-session NAME" |
| 882 | Apply to session name. |
| 883 | .TP |
| 884 | .BR "\-n, \-\-name NAME" |
| 885 | Name of the snapshot's output. |
| 886 | .TP |
| 887 | .BR "\-m, \-\-max-size SIZE" |
| 888 | Maximum size in bytes of the snapshot. The maxium size does not include the |
| 889 | metadata file. Human readable format is accepted: {+k,+M,+G}. For instance, |
| 890 | \-\-max-size 5M |
| 891 | |
| 892 | The minimum size of a snapshot is computed by multiplying the total amount of |
| 893 | streams in the session by the largest subbuffer size. This is to ensure |
| 894 | fairness between channels when extracting data. |
| 895 | .TP |
| 896 | .BR "\-C, \-\-ctrl-url URL" |
| 897 | Set control path URL. (Must use -D also) |
| 898 | .TP |
| 899 | .BR "\-D, \-\-data-url URL" |
| 900 | Set data path URL. (Must use -C also) |
| 901 | .RE |
| 902 | .PP |
| 903 | |
| 904 | .PP |
| 905 | \fBstart\fP [NAME] [OPTIONS] |
| 906 | .RS |
| 907 | Start tracing |
| 908 | |
| 909 | It will start tracing for all tracers for a specific tracing session. |
| 910 | If NAME is omitted, the session name is taken from the .lttngrc file. |
| 911 | |
| 912 | .B OPTIONS: |
| 913 | |
| 914 | .TP |
| 915 | .BR "\-h, \-\-help" |
| 916 | Show summary of possible options and commands. |
| 917 | .TP |
| 918 | .BR "\-\-list-options" |
| 919 | Simple listing of options |
| 920 | .RE |
| 921 | .PP |
| 922 | |
| 923 | .PP |
| 924 | \fBstop\fP [NAME] [OPTIONS] |
| 925 | .RS |
| 926 | Stop tracing |
| 927 | |
| 928 | It will stop tracing for all tracers for a specific tracing session. Before |
| 929 | returning, the command checks for data availability meaning that it will wait |
| 930 | until the trace is readable for the session. Use \-\-no-wait to avoid this |
| 931 | behavior. |
| 932 | |
| 933 | If NAME is omitted, the session name is taken from the .lttngrc file. |
| 934 | |
| 935 | .B OPTIONS: |
| 936 | |
| 937 | .TP |
| 938 | .BR "\-h, \-\-help" |
| 939 | Show summary of possible options and commands. |
| 940 | .TP |
| 941 | .BR "\-\-list-options" |
| 942 | Simple listing of options |
| 943 | .TP |
| 944 | .BR "\-\-no-wait" |
| 945 | Don't wait for data availability. |
| 946 | .RE |
| 947 | .PP |
| 948 | |
| 949 | .PP |
| 950 | \fBversion\fP |
| 951 | .RS |
| 952 | Show version information |
| 953 | |
| 954 | .B OPTIONS: |
| 955 | |
| 956 | .TP |
| 957 | .BR "\-h, \-\-help" |
| 958 | Show summary of possible options and commands. |
| 959 | .TP |
| 960 | .BR "\-\-list-options" |
| 961 | Simple listing of options |
| 962 | .RE |
| 963 | .PP |
| 964 | |
| 965 | .PP |
| 966 | \fBview\fP [SESSION_NAME] [OPTIONS] |
| 967 | .RS |
| 968 | View traces of a tracing session. By default, the babeltrace viewer |
| 969 | will be used for text viewing. If SESSION_NAME is omitted, the session |
| 970 | name is taken from the .lttngrc file. |
| 971 | |
| 972 | .B OPTIONS: |
| 973 | |
| 974 | .TP |
| 975 | .BR "\-h, \-\-help" |
| 976 | Show this help |
| 977 | .TP |
| 978 | .BR "\-\-list-options" |
| 979 | Simple listing of options |
| 980 | .TP |
| 981 | .BR "\-t, \-\-trace-path PATH" |
| 982 | Trace directory path for the viewer |
| 983 | .TP |
| 984 | .BR "\-e, \-\-viewer CMD" |
| 985 | Specify viewer and/or options to use This will completely override the |
| 986 | default viewers so please make sure to specify the full command. The |
| 987 | trace directory path of the session will be appended at the end to the |
| 988 | arguments |
| 989 | .RE |
| 990 | .PP |
| 991 | |
| 992 | .SH "JUL DOMAIN" |
| 993 | This section explains the JUL domain (\-j, \-\-jul) where JUL stands for Java |
| 994 | Util Logging. You can use that feature by using the \fBliblttng-ust-jul.so\fP |
| 995 | from the lttng-ust(3) project. |
| 996 | |
| 997 | The LTTng Java Agent uses JNI to link the UST tracer to the Java application |
| 998 | that uses the agent. Thus, it behaves similarly to the UST domain (\-u). When |
| 999 | enabling events with the JUL domain, you enable a Logger name that will then be |
| 1000 | mapped to a default UST tracepoint called \fBlttng_jul:jul_event\fP in the |
| 1001 | \fBlttng_jul_channel\fP. Using the lttng-ctl API, any JUL events must use the |
| 1002 | tracepoint event type (same as \-\-tracepoint). |
| 1003 | |
| 1004 | Because of the default immutable channel (\fBlttng_jul_channel\fP), the |
| 1005 | \fBenable-channel\fP command CAN NOT be used with the JUL domain thus not |
| 1006 | having any \-j option. |
| 1007 | |
| 1008 | For JUL event, loglevels are supported with the JUL ABI values. Use \fBlttng |
| 1009 | enable-event \-h\fP to list them. Wildcards are NOT supported except the "*" |
| 1010 | meaning all events (same as \-a). |
| 1011 | |
| 1012 | Exactly like the UST domain, if the Java application has the same UID as you, |
| 1013 | you can trace it. Same goes for the tracing group accessing root applications. |
| 1014 | |
| 1015 | Finally, you can list every Logger name that are available from JUL registered |
| 1016 | applications to the session daemon by using \fBlttng list \-j\fP. |
| 1017 | |
| 1018 | Here is an example on how to use this domain. |
| 1019 | |
| 1020 | .nf |
| 1021 | $ lttng list -j |
| 1022 | [...] |
| 1023 | $ lttng create aSession |
| 1024 | $ lttng enable-event -s aSession -j MyCustomLoggerName |
| 1025 | $ lttng start |
| 1026 | .fi |
| 1027 | |
| 1028 | More information can be found in the lttng-ust documentation, see |
| 1029 | java-util-logging.txt |
| 1030 | .PP |
| 1031 | |
| 1032 | .SH "EXIT VALUES" |
| 1033 | .PP |
| 1034 | On success 0 is returned and a positive value on error. Value of 1 means a command |
| 1035 | error, 2 an undefined command, 3 a fatal error and 4 a command warning meaning that |
| 1036 | something went wrong during the command. |
| 1037 | |
| 1038 | Any other value above 10, please refer to |
| 1039 | .BR "<lttng/lttng-error.h>" |
| 1040 | for a detailed list or use lttng_strerror() to get a human readable string of |
| 1041 | the error code. |
| 1042 | .PP |
| 1043 | |
| 1044 | .SH "ENVIRONMENT VARIABLES" |
| 1045 | |
| 1046 | .PP |
| 1047 | Note that all command line options override environment variables. |
| 1048 | .PP |
| 1049 | |
| 1050 | .PP |
| 1051 | .IP "LTTNG_SESSIOND_PATH" |
| 1052 | Allows one to specify the full session daemon binary path to lttng command line |
| 1053 | tool. You can also use \-\-sessiond-path option having the same effect. |
| 1054 | .PP |
| 1055 | |
| 1056 | .PP |
| 1057 | .IP "LTTNG_SESSION_CONFIG_XSD_PATH" |
| 1058 | Set the path in which the \fBsession.xsd\fP session configuration schema may be |
| 1059 | found. |
| 1060 | .PP |
| 1061 | |
| 1062 | .SH "SEE ALSO" |
| 1063 | .BR babeltrace(1), |
| 1064 | .BR lttng-ust(3), |
| 1065 | .BR lttng-sessiond(8), |
| 1066 | .BR lttng-relayd(8), |
| 1067 | |
| 1068 | .SH "BUGS" |
| 1069 | |
| 1070 | .PP |
| 1071 | If you encounter any issues or usability problem, please report it on our |
| 1072 | mailing list <lttng-dev@lists.lttng.org> to help improve this project or |
| 1073 | at https://bugs.lttng.org which is a bugtracker. |
| 1074 | .PP |
| 1075 | |
| 1076 | .SH "CREDITS" |
| 1077 | |
| 1078 | .PP |
| 1079 | lttng is distributed under the GNU General Public License version 2. See the file |
| 1080 | COPYING for details. |
| 1081 | .PP |
| 1082 | A Web site is available at http://lttng.org for more information on the LTTng |
| 1083 | project. |
| 1084 | .PP |
| 1085 | You can also find our git tree at http://git.lttng.org. |
| 1086 | .PP |
| 1087 | Mailing lists for support and development: <lttng-dev@lists.lttng.org>. |
| 1088 | .PP |
| 1089 | You can find us on IRC server irc.oftc.net (OFTC) in #lttng. |
| 1090 | .PP |
| 1091 | .SH "THANKS" |
| 1092 | |
| 1093 | .PP |
| 1094 | Thanks to Yannick Brosseau without whom this project would never have been so |
| 1095 | lean and mean! Also thanks to the Ericsson teams working on tracing which |
| 1096 | helped us greatly with detailed bug reports and unusual test cases. |
| 1097 | |
| 1098 | Thanks to our beloved packager Alexandre Montplaisir-Goncalves (Ubuntu and PPA |
| 1099 | maintainer) and Jon Bernard for our Debian packages. |
| 1100 | |
| 1101 | Special thanks to Michel Dagenais and the DORSAL laboratory at Polytechnique de |
| 1102 | Montreal for the LTTng journey. |
| 1103 | .PP |
| 1104 | .SH "AUTHORS" |
| 1105 | |
| 1106 | .PP |
| 1107 | lttng-tools was originally written by Mathieu Desnoyers, Julien Desfossez and |
| 1108 | David Goulet. More people have since contributed to it. It is currently |
| 1109 | maintained by David Goulet <dgoulet@efficios.com>. |
| 1110 | .PP |