From 1581c49bdd36572154b3dc20962ee594e4b0d8c7 Mon Sep 17 00:00:00 2001 From: Vadim Yanitskiy Date: Wed, 20 Nov 2019 23:20:30 +0700 Subject: logging/vty: do not print deprecated logging commands to stdout Yes, we don't really need to poison stdout, as some osmo-* binaries (like osmo-gapk) may want to use it for non-logging purposes. This printf() call looks like a debugging leftover. Change-Id: Ida35865b1c0bb3d3567918f8e89c6551c6b34103 --- src/vty/logging_vty.c | 1 - 1 file changed, 1 deletion(-) (limited to 'src/vty') diff --git a/src/vty/logging_vty.c b/src/vty/logging_vty.c index 88ee330a..96159433 100644 --- a/src/vty/logging_vty.c +++ b/src/vty/logging_vty.c @@ -1007,7 +1007,6 @@ void logging_vty_add_deprecated_subsys(void *ctx, const char *name) OSMO_ASSERT(cmd); cmd->string = talloc_asprintf(cmd, "logging level %s (debug|info|notice|error|fatal)", name); - printf("%s\n", cmd->string); cmd->func = log_deprecated_func; cmd->doc = LEVEL_STR "Deprecated Category\n"; -- cgit v1.2.3