* Thibault, Daniel (daniel.thiba...@drdc-rddc.gc.ca) wrote:
[...]
>On a somewhat related topic, I find the CTF (1.8.2) spec confusing
>in sections 5 and 6:
>
> > 5. Event Packet Header
> >
> > The event packet header consists of two parts: the "event packet header"
> > is the same for all
* Thibault, Daniel (daniel.thiba...@drdc-rddc.gc.ca) wrote:
> -Message d'origine-
> From: Mathieu Desnoyers
>
> > I having similar questions as Daniel about tracefile-size and
> > tracefile-count.
> >
> > For each stream, do we have max size used on disk = size * count or size
> > used
Here are proposed semantics for the tracefile-size/tracefile-count
enable-channel options (are they still planned for later inclusion in
lttng-tools?):
-C, --tracefile-size SIZE
This is a recent proposal (2013-Mar-08) that has yet to be added to the
command. Maximum size of each sto
-Message d'origine-
From: Mathieu Desnoyers
> I having similar questions as Daniel about tracefile-size and tracefile-count.
>
> For each stream, do we have max size used on disk = size * count or size used
> = size ?
My understanding is that the maximum size on disk of a stream (cha
* Julien Desfossez (jdesfos...@efficios.com) wrote:
> This patch introduces the tracefile_size and tracefile_count parameters
> to the enable-channel command and the API.
I having similar questions as Daniel about tracefile-size and
tracefile-count.
for each stream, do we have max size used on di
> @@ -78,6 +80,8 @@ static struct poptOption long_options[] = {
> {"read-timer", 0, POPT_ARG_INT, 0, OPT_READ_TIMER, 0, 0},
> {"list-options", 0, POPT_ARG_NONE, NULL, OPT_LIST_OPTIONS, NULL,
> NULL},
> {"output", 0, POPT_ARG_STRING, &opt_output, 0, 0, 0},
> +
