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 23:56:43 +0200	[thread overview]
Message-ID: <4F7B721B.5080202@ettoredelnegro.me> (raw)
In-Reply-To: <4F7B6A30.3020704@efficios.com>

On 3/4/2012 11:22 PM, David Goulet wrote:
> Actually it does. If you type: lttng create test -o /tmp/test
>
> /tmp/test is created and empty.
>
Yeah, that was meant as a reply for Ryan.
>
> > 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
>
> I've just tested it. The trace output directory, given without a full
> path, is
> created at the $PWD of the session daemon. If the directory exist, it will
> simply write the trace in it.
>
> So, the error you have are probably related to a location you don't
> have write
> access.....
>
> I agree that the relative path could be handle better and use the current
> directory of the user using "lttng".
I was missing the fact that the *daemon* creates the directory. Thanks
for clarify it.
Definitely use the current directory of lttng for relative paths would
be better.
>
> Thanks!
> David
>
>
Thanks,
Ettore



  reply	other threads:[~2012-04-03 21:56 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
2012-04-03 21:22     ` David Goulet
2012-04-03 21:56       ` Ettore Del Negro [this message]
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=4F7B721B.5080202@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