Fix: don't use newlines in logging message

Using explicit newlines ('\n') in a logging messages breaks the
logging output and makes it unnecessarily harder to read and parse the
LTTng daemons' logs.

Moreover, it is unnecessary to escape multi-line string literals.

Signed-off-by: Jérémie Galarneau <jeremie.galarneau@efficios.com>

diff --git a/src/bin/lttng-relayd/session.c b/src/bin/lttng-relayd/session.c
index 888bb88ebc53cc916dada51f23db5e011dc3ced2..c4a62c986946ac09f73fe66108b060b534915ff3 100644 (file)
--- a/src/bin/lttng-relayd/session.c
+++ b/src/bin/lttng-relayd/session.c
@@ -47,8 +47,8 @@ static int session_set_anonymous_chunk(struct relay_session *session)
                /* No output path defined */
                const char *home_dir = utils_get_home_dir();
                if (!home_dir) {
                /* No output path defined */
                const char *home_dir = utils_get_home_dir();
                if (!home_dir) {

-                       ERR("Home path not found.\n \
-                                       Please specify an output path using -o, --output PATH");
+                       ERR("Home path not found."
+                                       " Please specify an output path using -o, --output PATH");

                        ret = -1;
                        goto end;
                }
                        ret = -1;
                        goto end;
                }