From: marc-andre.laperle@ericsson.com (Marc-André Laperle)
Subject: [lttng-dev] Listing live sessions after a session is destroyed
Date: Wed, 29 Oct 2014 21:39:26 +0000 [thread overview]
Message-ID: <D381217948BF4C45AF756AFC995BEB9F1C2EBF68@eusaamb103.ericsson.se> (raw)
I have a viewer connected to relayd and attached to a session named "live". The session is started then destroyed. Then I list the sessions using the same viewer and it returns the destroyed session. If I try to attach to it, it returns a status LTTNG_VIEWER_ATTACH_ALREADY. I think this session should not be listed or there should be a status that indicates that the session doesn't exist anymore. Or is it expected that I create a new viewer before listing the sessions again?
Thank you for the help!
Marc-Andre
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lttng.org/pipermail/lttng-dev/attachments/20141029/5de9bbda/attachment.html>
next reply other threads:[~2014-10-29 21:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-29 21:39 Marc-André Laperle [this message]
2014-10-30 18:41 ` Jérémie Galarneau
2014-10-31 14:47 ` Marc-André Laperle
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=D381217948BF4C45AF756AFC995BEB9F1C2EBF68@eusaamb103.ericsson.se \
--to=marc-andre.laperle@ericsson.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