lttng-dev.lists.lttng.org archive mirror
 help / color / mirror / Atom feed
From: "Kramer, Zach via lttng-dev" <lttng-dev@lists.lttng.org>
To: lttng-dev <lttng-dev@lists.lttng.org>
Subject: [lttng-dev] Question about rotating session limitations
Date: Fri, 13 Aug 2021 07:28:14 +0000	[thread overview]
Message-ID: <DM6PR06MB61863EC46C9025E1C0250F3A91FA9@DM6PR06MB6186.namprd06.prod.outlook.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 831 bytes --]

Hello,

On https://lttng.org/man/1/lttng-rotate/v2.12/ one of the limitations is listed as:

The lttng rotate command only works when:

·         No channel was created with a configured trace file count or size limit (see the --tracefile-size and --tracefile-count options in lttng-enable-channel(1)<https://lttng.org/man/1/lttng-enable-channel/v2.12>).
However on v2.12.1 I am able to:

  1.  Create a userspace session
  2.  Create a channel w/ configured trace file count and size limit
  3.  Start tracing
  4.  lttng rotate

Within each chunk these restrictions are respected.

Therefore my question is what does this limitation actually mean? Is it more so in the direction that the archives will not respect these limits because the chunks accumulate? Or am I missing the point entirely?

Thanks,
Zach

[-- Attachment #1.2: Type: text/html, Size: 7890 bytes --]

[-- Attachment #2: Type: text/plain, Size: 156 bytes --]

_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

             reply	other threads:[~2021-08-13  7:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-13  7:28 Kramer, Zach via lttng-dev [this message]
2021-08-13 14:56 ` [lttng-dev] Question about rotating session limitations Jérémie Galarneau via lttng-dev

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=DM6PR06MB61863EC46C9025E1C0250F3A91FA9@DM6PR06MB6186.namprd06.prod.outlook.com \
    --to=lttng-dev@lists.lttng.org \
    --cc=Zach.Kramer@cognex.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).