Fix: don't wait for the load thread before serving client commands
authorJérémie Galarneau <jeremie.galarneau@efficios.com>
Wed, 16 May 2018 21:08:36 +0000 (17:08 -0400)
committerJérémie Galarneau <jeremie.galarneau@efficios.com>
Thu, 17 May 2018 03:38:44 +0000 (23:38 -0400)
commit3c3c4e5c9cd601b618092e75aba017ce6896408c
tree23ccde6a8be521c236d919433d614a967cb3b1c9
parentd741ba7f3241479e38278de12ce69f4bdd8b825d
Fix: don't wait for the load thread before serving client commands

Since the session loading thread uses the same communication than
the external clients, it should not be included in the set of
threads that must be launched before the sessiond starts to serve
client commands.

Since the "load session" thread is guaranteed to be the last
essential thread to be initialized, it can explicitly signal
the parents that the sessiond is ready once it is done auto-loading
session configurations.

This commit also adds a lengthy comment explaining the initialization
of the session daemon.

Signed-off-by: Jérémie Galarneau <jeremie.galarneau@efficios.com>
src/bin/lttng-sessiond/load-session-thread.c
src/bin/lttng-sessiond/lttng-sessiond.h
src/bin/lttng-sessiond/main.c
This page took 0.025655 seconds and 4 git commands to generate.