LTTng

Previously on a lttng 2.10 relayd/tools the following sequence is acceptable and result in a hooked babeltrace:

lttng create
lttng enable-event -u -a
babeltrace -i lttng-live net://localhost
babeltrace -i lttng-live net://localhost/the_session_path
lttng start

On lttng 2.11, the same sequence leave babeltrace unable to hook itself before a "lttng start" is issued.

Nothing describe the guarantee that we expose on that side but we do have to ask ourselves if this sequence of action is valid or not.

A scenario where the user want to make sure to get the event ASAP on babeltrace side might want to hook itself to the session before any event can be recorded.

This was found using the lttng-ivc project. The test code was adapted to a functioning sequence but this should require more discussion overall. This is in no way a major concern.

Cheers