Blame SOURCES/0007-SSSCTL-Allow-analyzer-to-work-without-SSSD-setup.patch

de2e0a
From f8704cc24eafe190e6c78dc21535f6029d51d647 Mon Sep 17 00:00:00 2001
de2e0a
From: Justin Stephenson <jstephen@redhat.com>
de2e0a
Date: Mon, 15 Aug 2022 16:17:59 -0400
de2e0a
Subject: [PATCH] SSSCTL: Allow analyzer to work without SSSD setup
de2e0a
de2e0a
Fixes an issue when the sssctl analyzer option is
de2e0a
used on systems where SSSD is not running or configured. This is
de2e0a
an expected use case when using --logdir option to analyze external
de2e0a
log files.
de2e0a
de2e0a
Resolves: https://github.com/SSSD/sssd/issues/6298
de2e0a
de2e0a
Reviewed-by: Alexey Tikhonov <atikhono@redhat.com>
de2e0a
---
de2e0a
 src/tools/sssctl/sssctl.c | 2 +-
de2e0a
 1 file changed, 1 insertion(+), 1 deletion(-)
de2e0a
de2e0a
diff --git a/src/tools/sssctl/sssctl.c b/src/tools/sssctl/sssctl.c
de2e0a
index 3816125ad..f18689f9f 100644
de2e0a
--- a/src/tools/sssctl/sssctl.c
de2e0a
+++ b/src/tools/sssctl/sssctl.c
de2e0a
@@ -296,7 +296,7 @@ int main(int argc, const char **argv)
de2e0a
         SSS_TOOL_COMMAND("logs-remove", "Remove existing SSSD log files", 0, sssctl_logs_remove),
de2e0a
         SSS_TOOL_COMMAND("logs-fetch", "Archive SSSD log files in tarball", 0, sssctl_logs_fetch),
de2e0a
         SSS_TOOL_COMMAND("debug-level", "Change SSSD debug level", 0, sssctl_debug_level),
de2e0a
-        SSS_TOOL_COMMAND("analyze", "Analyze logged data", 0, sssctl_analyze),
de2e0a
+        SSS_TOOL_COMMAND_FLAGS("analyze", "Analyze logged data", 0, sssctl_analyze, SSS_TOOL_FLAG_SKIP_CMD_INIT),
de2e0a
 #ifdef HAVE_LIBINI_CONFIG_V1_3
de2e0a
         SSS_TOOL_DELIMITER("Configuration files tools:"),
de2e0a
         SSS_TOOL_COMMAND_FLAGS("config-check", "Perform static analysis of SSSD configuration", 0, sssctl_config_check, SSS_TOOL_FLAG_SKIP_CMD_INIT),
de2e0a
-- 
de2e0a
2.37.1
de2e0a