Fix: sessiond: application channel creation failure stops start cmd
authorJérémie Galarneau <jeremie.galarneau@efficios.com>
Tue, 15 Oct 2019 20:56:22 +0000 (16:56 -0400)
committerJérémie Galarneau <jeremie.galarneau@efficios.com>
Tue, 15 Oct 2019 20:56:22 +0000 (16:56 -0400)
commitd767977450c6bf1fb18ce8bb653d6b6dfdb6bb68
treed4e5b64e99a394dbaf8a1b8bb6f52258ecd559e2
parent205339471d9653a2b011d3eafe3a711cf79a6aca
Fix: sessiond: application channel creation failure stops start cmd

The creation of an application's channel can fail when, for instance,
a context can't be created. This causes applications that would have
been started _after_ it to never be started.

This keeps the iteration going on error and starts all applications
that could be started. This is more in line with the behaviour of
2.10 (and earlier) since those channel creations would occur as
applications registered and not on tracing "start".

Signed-off-by: Jérémie Galarneau <jeremie.galarneau@efficios.com>
src/bin/lttng-sessiond/ust-app.c
This page took 0.032308 seconds and 4 git commands to generate.