Fix: path of snapshots with a relay and default URI
authorJulien Desfossez <jdesfossez@efficios.com>
Wed, 30 Aug 2017 18:06:42 +0000 (14:06 -0400)
committerJérémie Galarneau <jeremie.galarneau@efficios.com>
Mon, 13 Nov 2017 23:02:30 +0000 (18:02 -0500)
commit10d653513d572b8727d6935767a96c9dd82e4fe2
treee7bf7f9ddbe3d345bcbfae7c869aa821fa3ae4c5
parent25e9873d19b2846dc373fc7e854ef33e55033d35
Fix: path of snapshots with a relay and default URI

When recording a snapshot to a relay without custom URI (ex:
net://localhost vs net://localhost/custom), the snapshots end up being
stored in ~/lttng-traces/<hostname>/snapshot-XXX instead of being inside
the <session-name> folder like on local snapshots. We would expect the
path to be: ~/lttng-traces/<hostname>/<session-name>/snapshot-XXX

So there is a discrepancy between the local and remote behaviour. This
behaviour has been there since at least v2.6, maybe earlier.

Moreover, there is nothing that informs the user about the default
snapshot name, so it is not possible to know where a snapshot has been
stored.

After parsing the URI provided by the user, we now check if a custom
name was provided or copy the session name there. This is the same
operation performed in _lttng_create_session_ext.

Signed-off-by: Julien Desfossez <jdesfossez@efficios.com>
Signed-off-by: Jérémie Galarneau <jeremie.galarneau@efficios.com>
src/lib/lttng-ctl/lttng-ctl.c
This page took 0.025456 seconds and 4 git commands to generate.