Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: tracemein@gmail.com (Naren)
Subject: [ltt-dev] LTT Userspace problems
Date: Wed, 27 Jan 2010 22:55:38 +0100	[thread overview]
Message-ID: <19fa8ef31001271355w4e5a4e8k78f228ea9399488a@mail.gmail.com> (raw)
Message-ID: <20100127215538.cTocmenkjSpu7R0l2p9VG2mcpt2_yqEgnrPl7kWMg9E@z> (raw)
In-Reply-To: <4B607B54.90107@polymtl.ca>

Hi,

Yes, it worked after the creation of "socks" directory under "tmp".

1. I presume that tmp/socks will be automatically created by UST unlike the
manual creation done by me to make it   work.
2. Every time, the system restarts, the user created folders are deleted
hence the need to create the socks directory after every restart.

Can you clarify on the above mentioned points and whether it is by purpose
that tmp/socks directory needs to be created manually or is there something
wrong with the UST installation.

Regards,
Naren

On Wed, Jan 27, 2010 at 6:43 PM, Pierre-Marc Fournier <
pierre-marc.fournier at polymtl.ca> wrote:

> As the message says:
> Error initializing named socket (/tmp/socks/12293). Check that directory
> exists and that it is writable.
>
> Are you sure /tmp/socks exists and that it is writable?
>
> pmf
>
> Mathieu Desnoyers wrote:
> > I'm forwarding this to Pierre-Marc.
> >
> > Thanks for the report,
> >
> > Mathieu
> >
> > * Naren (tracemein at gmail.com) wrote:
> >> Hi,
> >>
> >> I've been facing problems with userspace tracing. During the execution
> of
> >> the sample file, i am getting the error as specified in the link.
> >>
> >> http://pastebin.ca/1765208
> >>
> >> Linux: Ubuntu 9.1
> >>
> >> Kernel Version: 2.6.30
> >>
> >> Lttng Version: 0.159
> >>
> >> UST version: 0.1
> >>
> >> Lttv version : 0.12.20
> >>
> >> For the sample test c code , click this link http://pastebin.ca/1765210
> >>
> >> Regards
> >> Naren
> >
> >> _______________________________________________
> >> ltt-dev mailing list
> >> ltt-dev at lists.casi.polymtl.ca
> >> http://lists.casi.polymtl.ca/cgi-bin/mailman/listinfo/ltt-dev
> >
> >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.casi.polymtl.ca/pipermail/lttng-dev/attachments/20100127/732a4b9d/attachment-0002.htm>


  reply	other threads:[~2010-01-27 21:55 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-25 15:12 Naren
2010-01-25 15:12 ` Naren
2010-01-25 15:12 ` Naren
2010-01-25 15:30 ` Mathieu Desnoyers
2010-01-27 17:43   ` Pierre-Marc Fournier
2010-01-27 21:55     ` Naren [this message]
2010-01-27 21:55       ` Naren
2010-01-27 21:55       ` Naren
2010-01-27 22:16       ` Douglas Santos
2010-01-27 22:43         ` Naren
2010-01-27 22:43           ` Naren
2010-01-27 22:43           ` Naren
2010-01-28 13:59           ` Mathieu Desnoyers
2010-01-28 15:32             ` Douglas Santos
2010-01-28 17:37               ` Mathieu Desnoyers
2010-01-28 17:39               ` Pierre-Marc Fournier
2010-01-28 17:35       ` Pierre-Marc Fournier

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=19fa8ef31001271355w4e5a4e8k78f228ea9399488a@mail.gmail.com \
    --to=tracemein@gmail.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