Fix. add limitation to man page
[lttng-tools.git] / doc / man / lttng-sessiond.8
CommitLineData
6991b181
DG
1.TH "LTTNG-SESSIOND" "8" "January 31, 2012" "" ""
2
3.SH "NAME"
4lttng-sessiond \(em LTTng 2.0 central tracing registry session daemon.
5
6.SH "SYNOPSIS"
7
8.PP
9.nf
10lttng-sessiond [OPTIONS]
11.fi
12.SH "DESCRIPTION"
13
14.PP
15The LTTng project aims at providing highly efficient tracing tools for Linux.
16It's tracers help tracking down performance issues and debugging problems
17involving multiple concurrent processes and threads. Tracing across multiple
18systems is also possible.
19
fa072eae 20The session daemon, acting as a tracing registry, allow you to interact with
6991b181
DG
21multiple tracers (kernel and user-space) inside the same container, a tracing
22session. Trace can be gathered from the kernel and/or instrumented applications
95dc6256 23(lttng-ust(3)). Aggregating those traces is done using a viewer, like the
fa072eae 24babeltrace(1) text viewer.
6991b181
DG
25
26In order to trace the kernel, the session daemon needs to be running as root.
27LTTng provides the use of a \fBtracing group\fP (default: tracing). Whomever is
28in that group can interact with the root session daemon and thus trace the
29kernel. Session daemons can co-exist meaning that you can have a session daemon
fa072eae
YB
30running as Alice that can be used to trace her applications along side with a
31root daemon or even a Bob daemon. We highly recommend to start the session
6991b181
DG
32daemon at boot time for stable and long term tracing.
33
34The session daemon is in charge of managing trace data consumers by spawning
fa072eae 35them when the time has come. The user don't need to manage the lttng-consumerd.
6991b181
DG
36.SH "OPTIONS"
37
38.PP
39This program follow the usual GNU command line syntax with long options starting with
40two dashes. Below is a summary of the available options.
41.PP
42
43.TP
44.BR "-h, --help"
45Show summary of possible options and commands
46.TP
47.BR "-v, --verbose"
48Increase verbosity
49
50There is three debugging level which will print on stderr. Maximum verbosity is
51\fB-vvv\fP.
52.TP
53.BR " --verbose-consumer"
54Verbose mode for consumer. Activate DBG() macro.
55.TP
56.BR "-d, --daemonize"
57Start as a daemon
58.TP
59.BR "-g, --group=NAME"
60Specify the tracing group name. (default: tracing)
61.TP
62.BR "-V, --version"
63Show version number
64.TP
65.BR "-S, --sig-parent"
66Send SIGCHLD to parent pid to notify readiness.
67
68This is used by \fBlttng(1)\fP to get notified when the session daemon is ready
fa072eae 69to accept command. When building a third party tool over liblttng-ctl, this option
6991b181
DG
70can be very handy to synchronize the control tool and the session daemon.
71.TP
72.BR "-q, --quiet"
73No output at all.
74.TP
75.BR " --no-kernel"
76No kernel tracer support
77.TP
78.BR "-c, --client-sock=PATH"
79Specify path for the client unix socket
80.TP
81.BR "-a, --apps-sock PATH"
82Specify path for apps unix socket
83.TP
84.BR " --kconsumerd-err-sock=PATH"
85Specify path for the kernel consumer error socket
86.TP
87.BR " --kconsumerd-cmd-sock=PATH
88Specify path for the kernel consumer command socket
89.TP
90.BR " --ustconsumerd32-err-sock=PATH
91Specify path for the 32-bit UST consumer error socket
92.TP
93.BR " --ustconsumerd64-err-sock=PATH
94Specify path for the 64-bit UST consumer error socket
95.TP
96.BR " --ustconsumerd32-cmd-sock=PATH
97Specify path for the 32-bit UST consumer command socket
98.TP
99.BR " --ustconsumerd64-cmd-sock=PATH
100Specify path for the 64-bit UST consumer command socket
101.TP
102.BR " --consumerd32-path=PATH
103Specify path for the 32-bit UST consumer daemon binary
104.TP
105.BR " --consumerd32-libdir=PATH
106Specify path for the 32-bit UST consumer daemon libraries
107.TP
108.BR " --consumerd64-path=PATH
109Specify path for the 64-bit UST consumer daemon binary
110.TP
111.BR " --consumerd64-libdir=PATH
112Specify path for the 64-bit UST consumer daemon libraries
113.SH "ENVIRONMENT VARIABLES"
114
115.PP
fa072eae 116Note that all command line options will override environment variables.
6991b181
DG
117.PP
118
119.PP
120.IP "LTTNG_CONSUMERD32_BIN"
fa072eae 121Specify the 32-bit consumer binary path. \fB--consumerd32-path\fP
6991b181
DG
122override this variable.
123.IP "LTTNG_CONSUMERD64_BIN"
fa072eae 124Specify the 64-bit consumer binary path. \fB--consumerd64-path\fP
6991b181
DG
125override this variable.
126.IP "LTTNG_CONSUMERD32_LIBDIR"
fa072eae 127Specifiy the 64-bit library path containing libconsumer.so.
6991b181
DG
128\fB--consumerd32-libdir\fP override this variable.
129.IP "LTTNG_CONSUMERD64_LIBDIR"
fa072eae 130Specifiy the 32-bit library path containing libconsumer.so.
6991b181 131\fB--consumerd64-libdir\fP override this variable.
2d85a600
MD
132.IP "LTTNG_DEBUG_NOCLONE"
133Debug-mode disabling use of clone/fork. Insecure, but required to allow
134debuggers to work with sessiond on some operating systems.
6991b181
DG
135.SH "SEE ALSO"
136
137.PP
138babeltrace(1), lttng-ust(3), lttng(1)
139.PP
95dc6256
DG
140
141.SH "LIMITATIONS"
142
143.PP
144For unprivileged user running lttng-sessiond, the maximum number of file
145descriptors per process is usually 1024. This limits the number of traceable
146applications since for each instrumented application there is two file
147descriptors per-CPU and one more socktet for bidirectional communication.
148
149For the root user, the limit is bumped to 65535. Future version will deal with
150this limitation.
151.PP
152
6991b181
DG
153.SH "BUGS"
154
155.PP
fa072eae 156No show stopper bugs are known yet in this version.
6991b181
DG
157
158If you encounter any issues or usability problem, please report it on our
159mailing list <lttng-dev@lists.lttng.org> to help improve this project.
160.SH "CREDITS"
161
162.PP
c9e32613 163lttng-sessiond is distributed under the GNU General Public License version 2. See the
6991b181
DG
164file COPYING for details.
165.PP
166A Web site is available at http://lttng.org for more information on the LTTng
167project.
168.PP
169You can also find our git tree at http://git.lttng.org.
170.PP
171Mailing lists for support and development: <lttng-dev@lists.lttng.org>.
172.PP
173You can find us on IRC server irc.oftc.net (OFTC) in #lttng.
174.PP
175.SH "THANKS"
176
177.PP
178Thanks to Yannick Brosseau without whom this project would never have been so
95dc6256
DG
179lean and mean! Also thanks to the Ericsson teams working on tracing which helped
180us greatly with detailed bug reports and unusual test cases.
6991b181
DG
181
182Thanks to our beloved packager Alexandre Montplaisir-Goncalves (Ubuntu and PPA
183maintainer) and Jon Bernard for our Debian packages.
184
185Special thanks to Michel Dagenais and the DORSAL laboratory at Polytechnique de
186Montreal for the LTTng journey.
c9e32613 187.PP
6991b181
DG
188.SH "AUTHORS"
189
190.PP
191lttng-tools was originally written by Mathieu Desnoyers, Julien Desfossez and
192David Goulet. More people have since contributed to it. It is currently
193maintained by David Goulet <dgoulet@efficios.com>.
194.PP
This page took 0.029823 seconds and 4 git commands to generate.