From 3d97f2645356adca1e9e6eeca4f735a1acbed15d Mon Sep 17 00:00:00 2001 From: Michal Zidek Date: Mon, 19 Nov 2012 13:10:39 +0100 Subject: debug: print fatal and critical errors if debug level is unresolved If global variable debug_level has value SSSDBG_UNRESOLVED, we should print at least fatal and critical errors. https://fedorahosted.org/sssd/ticket/1345 --- src/monitor/monitor.c | 6 ------ 1 file changed, 6 deletions(-) (limited to 'src/monitor') diff --git a/src/monitor/monitor.c b/src/monitor/monitor.c index 40f1f56c..71f91572 100644 --- a/src/monitor/monitor.c +++ b/src/monitor/monitor.c @@ -2752,12 +2752,6 @@ int main(int argc, const char *argv[]) /* Parse config file, fail if cannot be done */ ret = load_configuration(tmp_ctx, config_file, &monitor); if (ret != EOK) { - /* if debug level has not been set, set it manually to make these - * critical failures visible */ - if (debug_level == SSSDBG_UNRESOLVED) { - debug_level = SSSDBG_MASK_ALL; - } - if (ret == EPERM) { DEBUG(1, ("Cannot read configuration file %s\n", config_file)); sss_log(SSS_LOG_ALERT, -- cgit