From 334dfcb7fdb6c4fabb16eea4fb25cf344c063579 Mon Sep 17 00:00:00 2001 From: =?utf8?q?J=C3=A9r=C3=A9mie=20Galarneau?= Date: Tue, 3 Sep 2019 18:20:01 -0400 Subject: [PATCH] Fix: don't use newlines in logging message MIME-Version: 1.0 Content-Type: text/plain; charset=utf8 Content-Transfer-Encoding: 8bit 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 --- src/bin/lttng-relayd/session.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) 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; } -- 2.34.1