Fix: path of snapshots with a relay and default URI
authorJulien Desfossez <jdesfossez@efficios.com>
Tue, 29 Aug 2017 18:52:59 +0000 (14:52 -0400)
committerJulien Desfossez <jdesfossez@efficios.com>
Tue, 29 Aug 2017 18:56:41 +0000 (14:56 -0400)
commitee4b2ecea2ead25da9873a6a365479dd8df1fe5c
tree0ccc0aee5dda3cd77fa53cc6e705dc6ee67c328a
parent7de30b986cb8b2975c02c39a675646aaae1ba942
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>
src/lib/lttng-ctl/lttng-ctl.c
This page took 0.028911 seconds and 5 git commands to generate.