From: Jérémie Galarneau <jeremie.galarneau@efficios.com>
Date: Tue, 3 Sep 2019 22:20:01 +0000 (-0400)
Subject: Fix: don't use newlines in logging message
X-Git-Tag: v2.11.0-rc3~38
X-Git-Url: https://git.lttng.org./?a=commitdiff_plain;h=3d9ba3ec5a416b0fc9c76f138a44b41558f3f4da;p=lttng-tools.git

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 888bb88eb..c4a62c986 100644
--- 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) {
-			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;
 		}