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

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