Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: ettore@ettoredelnegro.me (Ettore Del Negro)
Subject: [lttng-dev] lttng create --output problem
Date: Tue, 03 Apr 2012 22:26:23 +0200	[thread overview]
Message-ID: <4F7B5CEF.5070504@ettoredelnegro.me> (raw)
In-Reply-To: <4F7B5981.8080002@efficios.com>

Hello,
actually 'lttng create --output dir session_name' should at least create
an empty directory with the chosen name. First of all try not to choose
an already existing directory so you can check whether it is created or not.

Anyway, i just noticed a problem with relative paths:
(~)> lttng
LTTng Trace Control 2.0.0-rc2
(~)> lttng create --output traces session
Error: Create directory failed
(~)> lttng create --output ./traces session
Error: Create directory failed
(~)> lttng create --output /root/traces session
Session session created.
Traces will be written in /root/traces

Is this expected?

Regards,
Ettore

On 3/4/2012 10:11 PM, David Goulet wrote:
> Hi Ryan,
>
> Well, the --output works on our test suites so it might be something
> you do that
> does not create the trace.
>
> Simply using create, start and stop will produce nothing. You have to
> at least
> enable events for trace files to be created since they are opened by
> the consumer.
>
> Can you try "lttng enable-events -a -k" (enabling all kernel events)
> after the
> create session and tell me if it works for you? (or use user space
> tracing,
> whatever works for you).
>
> If not, add "-vvv" to the lttng command for debug output and also for the
> session daemon.
>
> # lttng-sessiond -vvv
> # lttng -vvv ...
>
> Thanks!
> David
>
> On 12-04-03 04:02 PM, Ryan.Kyser at jci.com wrote:
>
> > Whenever I try using the --output flag for creating a new session,
> it doesn't
> > seem to use the location specified. Additionally, if I do a find on
> the entire
> > file system, no files are found that start with session name
> specified. This
> > seems like a bug to me ... or am I doing something wrong?
>
> > //---------------------------------------
> > // Log
> > //---------------------------------------
>
> > / # lttng create --output /tmp new3
> > Session new3 created.
> > Traces will be written in /tmp
> > / # lttng start
> > Tracing started for session new3
> > / # lttng stop
> > Tracing stopped for session new3
> > / # ls /tmp
> > wayland-0       wayland-0.lock
>
>
> > Thank you,
> > Ryan Kyser
>
>
>
> > _______________________________________________
> > lttng-dev mailing list
> > lttng-dev at lists.lttng.org
> > http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
>
> _______________________________________________
> lttng-dev mailing list
> lttng-dev at lists.lttng.org
> http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
>


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lttng.org/pipermail/lttng-dev/attachments/20120403/149d6ffa/attachment.html>


  reply	other threads:[~2012-04-03 20:26 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-03 20:02 Ryan.Kyser
2012-04-03 20:11 ` David Goulet
2012-04-03 20:26   ` Ettore Del Negro [this message]
2012-04-03 21:22     ` David Goulet
2012-04-03 21:56       ` Ettore Del Negro
2012-04-03 21:58         ` David Goulet
2012-04-03 22:10         ` Mathieu Desnoyers
2012-04-03 20:38   ` Ryan.Kyser
2012-04-03 21:06     ` David Goulet
2012-04-03 21:19       ` Mathieu Desnoyers
2012-04-04 14:05         ` Ryan.Kyser
2012-04-04 20:01         ` Ryan.Kyser
2012-04-06 16:02           ` Mathieu Desnoyers
2012-04-06 16:31             ` Mathieu Desnoyers
2012-04-09 19:27               ` Ryan.Kyser
2012-04-09 19:38                 ` Mathieu Desnoyers
2012-04-09 19:20             ` Ryan.Kyser

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=4F7B5CEF.5070504@ettoredelnegro.me \
    --to=ettore@ettoredelnegro.me \
    /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